)]}'
{
  "commit": "b11f07783d88c28d72dbfcc15161cf1aed239aef",
  "tree": "e241b3e9e3749b2e02983de5a9b46b87cdc0d885",
  "parents": [
    "7fd51912fa042993de34b126b1774b45bbc6c5a0"
  ],
  "author": {
    "name": "Richard Levasseur",
    "email": "rlevasseur@google.com",
    "time": "Sun Dec 08 18:50:37 2024 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Dec 09 02:50:37 2024 +0000"
  },
  "message": "fix: define rules_python_internal earlier so Bazel 9 doesn\u0027t try to use PyInfo et al builtins (#2485)\n\nFor Bazel 9 workspace builds, if `@rules_python_internal` isn\u0027t defined\nearly enough,\nan earlier version of `@rules_python` gets defined and the logic to not\nuse the builtin\nPyInfo et al symbols doesn\u0027t occur. Since Bazel 9 doesn\u0027t have these\nbuiltins, an error\noccurs.\n\nThis seems to only happen if the main module is rules_python. The\nexample workspaces don\u0027t\nsee to have an issue. I\u0027m not sure why, but it seems similar to the\nbehavior where\nautoloading is disabled for specific repos, rules_python among them.\n\nTo fix, move the `@rules_python_internal` repo definition to be earlier\nin the WORKSPACE\nprocessing. With that repo defined, the conditional logic takes place,\nand things seem\nto be happy.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "80196815a06c3aa3aad7552fb04a3636a45bb026",
      "old_mode": 33188,
      "old_path": "internal_dev_deps.bzl",
      "new_id": "e76ee48e83965b5a6683fcf1ed478191323b65a3",
      "new_mode": 33188,
      "new_path": "internal_dev_deps.bzl"
    },
    {
      "type": "modify",
      "old_id": "554ff926f2e21d580fb03350a6544815ff99d34f",
      "old_mode": 33188,
      "old_path": "internal_dev_setup.bzl",
      "new_id": "26edcb9abb7dea9fe988f0a20b9fabdf2447e54f",
      "new_mode": 33188,
      "new_path": "internal_dev_setup.bzl"
    }
  ]
}