)]}'
{
  "commit": "87f19cfdacafc30c9baca60166e249cc8fe383e6",
  "tree": "2f4b110734306df5365015c84dedeeeb8f30db18",
  "parents": [
    "1e0f5eefabde3f8b1a6609fd67c10b1f5bb7601f"
  ],
  "author": {
    "name": "David Ostrovsky",
    "email": "david@ostrovsky.org",
    "time": "Fri Feb 06 08:21:01 2026 +0100"
  },
  "committer": {
    "name": "David Ostrovsky",
    "email": "david@ostrovsky.org",
    "time": "Fri Feb 06 08:31:11 2026 +0100"
  },
  "message": "Bazel: enforce strict MODULE.bazel.lock synchronization\n\nThis prevents accidental desynchronization between MODULE.bazel and\nMODULE.bazel.lock by failing the build when the lockfile is out of\ndate, instead of silently updating it.\n\nEnforcing strict lockfile mode ensures that such inconsistencies are\ncaught early and that any lockfile update is always intentional and\nexplicitly reviewed.\n\nTo update the lockfile explicitly, run:\n\n  bazelisk mod deps --lockfile_mode\u003dupdate\n\nThe developer documentation has not been updated, as there is currently\nno Bazel build documentation available for JGit.\n\nTest Plan\n- Bump a Bazel module in MODULE.bazel (e.g. rules_java to 8.16.1).\n- Do not update MODULE.bazel.lock.\n- Run:\n    bazelisk build org.eclipse.jgit:jgit\n- The build fails as expected with an error suggesting:\n    bazelisk mod deps --lockfile_mode\u003dupdate\n\nChange-Id: Icafcf359eb3f2a4a2dce16d15c9a494a2e30f7cc\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5bf3ef85e06d7b375a939ae580d441b2658d9833",
      "old_mode": 33188,
      "old_path": ".bazelrc",
      "new_id": "385a71d7cb02be02ca15fb7d8ed6d9f1fdf99033",
      "new_mode": 33188,
      "new_path": ".bazelrc"
    }
  ]
}