)]}'
{
  "commit": "b66e78bad319b5107a5d1be67343a5705360e87a",
  "tree": "d58f84b9baa888a8cf0a981f82766e696ef6dd35",
  "parents": [
    "d194e06017497c753e0dd76e5e33e82a2f4d0b0b"
  ],
  "author": {
    "name": "wyv",
    "email": "wyv@google.com",
    "time": "Tue Jul 28 15:01:47 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Tue Jul 28 15:02:38 2026 -0700"
  },
  "message": "Fix release script for rolling releases\n\nFollow-up to https://github.com/bazelbuild/bazel/commit/27ac55328ac3dab00715be231c4ab83a2f13305b. That CL made it so that the release script can only be run from the last RC branch (release-X.Y.ZrcN), and that it must be at the same commit as the release branch (release-X.Y.Z).\n\nThis broke rolling releases because rolling releases only have an RC1 branch (release-X.0.0-preXXXXXXrc1), and no corresponding release branch. So this CL essentially wraps all the stuff introduced by https://github.com/bazelbuild/bazel/commit/27ac55328ac3dab00715be231c4ab83a2f13305b in a \"is rolling release\" check.\n\nPiperOrigin-RevId: 955490938\nChange-Id: I024c656c28f931f5c1770de37006978c647db51f\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1a66139644c6bb69cadefaa194bec073c5436c8e",
      "old_mode": 33261,
      "old_path": "scripts/release/release.sh",
      "new_id": "1053d95daf21c3fb8b3a4a94721fdb4e9fadf638",
      "new_mode": 33261,
      "new_path": "scripts/release/release.sh"
    }
  ]
}