)]}'
{
  "commit": "32d7a24d45eae7430b38733353e3ee77583d2da8",
  "tree": "e707fbdae0813f4459bbb5f2e66791a89e3b0f29",
  "parents": [
    "e3655c2bee36225366a89554a5a2628237c84f00"
  ],
  "author": {
    "name": "Malte Poll",
    "email": "1780588+malt3@users.noreply.github.com",
    "time": "Thu Aug 07 03:39:18 2025 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Aug 07 01:39:18 2025 +0000"
  },
  "message": "fix: use \"command -v\" to find interpreter in $PATH (#3150)\n\nIn some environments, `which` doesn\u0027t work correctly under Bazel, while\n`command -v` does.\nI think the difference is that `command` is a shell builtin (and POSIX\ncompliant), whereas `which` is not:\n\n```\n$ sh -c \u0027builtin command -v python3\u0027\n/usr/bin/python3\n\n$ sh -c \u0027builtin which python3\u0027\nsh: line 1: builtin: which: not a shell builtin\n```\n\nWhile `command -v` performs fewer checks under the hood, it is more\nportable.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "422e399026ac12255f20a31e2453887aa8508236",
      "old_mode": 33188,
      "old_path": "CHANGELOG.md",
      "new_id": "08991c610709428773935a1ddf2ace226050a786",
      "new_mode": 33188,
      "new_path": "CHANGELOG.md"
    },
    {
      "type": "modify",
      "old_id": "dd4d648d126c34244a00a55c6c2dd35ce8bfd056",
      "old_mode": 33261,
      "old_path": "python/private/runtime_env_toolchain_interpreter.sh",
      "new_id": "c78cfe1a9b551ccfbf1e268c55027f46e591ba73",
      "new_mode": 33261,
      "new_path": "python/private/runtime_env_toolchain_interpreter.sh"
    }
  ]
}