)]}'
{
  "commit": "6626e6acfee0d22423e258bdcfc8e54045b0d88d",
  "tree": "3023866731546f697ac2c887c691a5ea4ac26dfb",
  "parents": [
    "488ce6bc486ce5755fb151ce54f1214c7002fe55"
  ],
  "author": {
    "name": "Keith Smiley",
    "email": "keithbsmiley@gmail.com",
    "time": "Mon Sep 15 10:32:24 2025 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Sep 15 10:32:24 2025 -0700"
  },
  "message": "[bazel] Update tblgen rules to support path-mapping (#158354)\n\nPath mapping is a feature of bazel that allows actions to be\ndeduplicated across bazel transitions if they are otherwise identical.\nThis is helpful if you build a binary in N transitions, where the\nsettings differences are irrelevant to this action. In our case we build\nmultiple python native extensions transitioning on the python version\nthey target, and before this change would run each of these actions once\nper python version even though the outputs would be identical.\n\nThis is a no-op unless `--experimental_output_paths\u003dstrip` is passed.\n\nThe changes here are just enough to make bazel automatically remap the\npaths, which is done by how you use the args object. The core change is\nthat instead of carrying around paths that have `ctx.bin_dir` hardcoded\nin the strings. This is done by mapping them with the output file\nobject\u0027s root path when adding them to the args.\n\nAs a side effect this drops the genfiles_dir, but that has been the same\nas bin_dir for a long time so hopefully that\u0027s a no-op for folks.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c94935216e0e96be54a47950aba5ef7eecdbeca0",
      "old_mode": 33188,
      "old_path": "utils/bazel/llvm-project-overlay/mlir/tblgen.bzl",
      "new_id": "35888aac37e17b4948c740b23c25677cb3e936c1",
      "new_mode": 33188,
      "new_path": "utils/bazel/llvm-project-overlay/mlir/tblgen.bzl"
    }
  ]
}