)]}'
{
  "commit": "b764503a883be0fc0738f64fb6c6d4d07b59fb9c",
  "tree": "fae6698480785d9447db450fae527ca605afca5e",
  "parents": [
    "30a6f8da464b461446b376c9b7f7e78111772024"
  ],
  "author": {
    "name": "Jeff Hodges",
    "email": "jeff@somethingsimilar.com",
    "time": "Mon Nov 03 22:42:32 2025 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Nov 04 07:42:32 2025 +0100"
  },
  "message": "correct macOS Tahoe 26 build via apple_support (#4500)\n\n**What type of PR is this?**\n\nBug fix\n\n**What does this PR do? Why is it needed?**\n\nAll of rules_go tests were failing on macOS Tahoe 26 due to `missing\nLC_UUID load command` in the clang binary built and in other tools. Many\ntools from Go to bazel itself have had to drop various workarounds for\nthese kinds of linker problems in the run-up to macOS Tahoe (see\nhttps://github.com/bazelbuild/apple_support/commit/44c43c715a and\nhttps://github.com/bazelbuild/bazel/pull/27014)\n\nTo fix this, we bump the version of build_bazel_apple_support (a.k.a.\napple_support in Bazel Central Registry) to 1.24.3 in WORKSPACE. We also\nhave to move the build_bazel_apple_support dependency above the\nllvm_toolchain call in order to make sure that version is actually used.\n\nIt\u0027s possible we should also upgrade the llvm_toolchain to something\nmore modern to handle some of our deps problems. The current llvm used\nby rules_go is 8.0.0 and is from 2019. The latest llvm version that\ntoolchains_llvm supports in its latest release 1.5.0 is llvm 21.1.0.\n\n\n**Which issues(s) does this PR fix?**\n\nFixes #4499",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a74a1f202fdaf1450a55cfe3a37b22e403571817",
      "old_mode": 33188,
      "old_path": "WORKSPACE",
      "new_id": "1ef9e500f4e13d23a5d9844c0d5fb7b139b06259",
      "new_mode": 33188,
      "new_path": "WORKSPACE"
    }
  ]
}