)]}'
{
  "commit": "6b85867813a69a3597a10967a16c7b80a8bc7c28",
  "tree": "f0958389a94c2c7a06326059431a26bf5a3279c8",
  "parents": [
    "674ce0745dea93e54865d9cfb846510b30475969"
  ],
  "author": {
    "name": "Tyler Yankee",
    "email": "tyler.yankee@kitware.com",
    "time": "Fri Oct 30 15:25:07 2026 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Oct 30 15:25:07 2026 +0000"
  },
  "message": "fix: tolerate absolute interpreter paths for lock update (#4384)\n\nSince #4029, the `lock` macro defaults the `directory` to the package\nname, and attempts to resolve the path to the Python interpreter via\nrelative path after `uv` changes into that directory. This is fine for\nhermetic Python, but it doesn\u0027t respect the case that `interpreter_path`\nis absolute.\n\nIf we have an absolute path to an interpreter, it doesn\u0027t need to\ninvolve `--directory`, so avoid the prefix altogether.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "84e4cbbc1293cb2534107dfa9182b751bfd7229d",
      "old_mode": 33188,
      "old_path": "python/uv/private/lock.bzl",
      "new_id": "ddb60d000608947028f8eaa13103833cbda6ee99",
      "new_mode": 33188,
      "new_path": "python/uv/private/lock.bzl"
    },
    {
      "type": "modify",
      "old_id": "f14d784ebff22b403bc81c6bb56e64fb61abf769",
      "old_mode": 33188,
      "old_path": "tests/uv/lock/lock_tests.bzl",
      "new_id": "f1aee2fdb15d4e6e796452486b4a4f66d5a101a0",
      "new_mode": 33188,
      "new_path": "tests/uv/lock/lock_tests.bzl"
    }
  ]
}