)]}'
{
  "commit": "c3e6caceec3b6f9550021fb11f3932369d7164bd",
  "tree": "f7bdeed4083ef53d30a9fbcb5a0c7eca1eacd571",
  "parents": [
    "0cdcecb2ee3a1da92f95ba0af036f20fa4179fb5"
  ],
  "author": {
    "name": "Fabian Meumertzheim",
    "email": "fabian@meumertzhe.im",
    "time": "Tue Oct 17 09:40:10 2023 +0200"
  },
  "committer": {
    "name": "Fabian Meumertzheim",
    "email": "fabian@meumertzhe.im",
    "time": "Tue Oct 17 09:40:10 2023 +0200"
  },
  "message": "Revert \"Reference `platformclasspath` in `@bazel_tools`\"\n\nThis reverts commit 54e89daeacd9728f45b4c16b3834e16d5f40e11c.\n\nGoing through `@bazel_tools` to reference the bootstrap classpath is no\nlonger needed with Bazel 7, which always uses toolchain macros that\ndefine the required bootstrap runtime toolchains.\n\nSince the original problem didn\u0027t arise with Bzlmod, where the Java\ntoolchains have always come from rules_java rather than bazel_tools,\nthis fixes https://github.com/bazelbuild/bazel/issues/19837 for Bazel\nitself by allowing it to use the new bootstrap classpath rule while\nstill being built with Bazel 6.4.0.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8e281872f31ccc3a294bdda620e106c70c4dac07",
      "old_mode": 33188,
      "old_path": "toolchains/default_java_toolchain.bzl",
      "new_id": "b6a65263c17a84e05501a745081d3a1d90d06ed3",
      "new_mode": 33188,
      "new_path": "toolchains/default_java_toolchain.bzl"
    }
  ]
}