)]}'
{
  "commit": "6c38b90ef18ecfb0e2ae19a885553ee4a1b0a84e",
  "tree": "921e0b11a07160463f45ae5f70607d47a05d09aa",
  "parents": [
    "14f5cfd604f2889c673c512d9bf549a2b6f1234c"
  ],
  "author": {
    "name": "cpovirk",
    "email": "cpovirk@google.com",
    "time": "Mon Jul 06 20:33:37 2026"
  },
  "committer": {
    "name": "Google Java Core Libraries",
    "email": "java-libraries-firehose+copybara@google.com",
    "time": "Mon Jul 06 20:37:16 2026"
  },
  "message": "Use `cancel-in-progress` instead of `styfle/cancel-workflow-action`.\n\nAdvantages:\n- We don\u0027t need to grant write permissions to a third-party action (or even use it at all).\n  - Not that I have any reason to think it\u0027s likely to be a problem, but strange things happen sometimes.\n- One less action means one less thing for us to merge Dependabot updates for.\n- The new approach can easily allow CI for merged trunk commits to continue even after other trunk commits are merged, while still stopping PR CI when new changes are pushed.\n  - This is especially nice because cancellations (at least those from `styfle/cancel-workflow-action`, maybe in general) show up as _failures_. It\u0027s nice to be able to pick out _real_ failures (e.g., those fixed by cl/925609698 and cl/943404496) without sorting through cancellations.\n- All else being equal, it\u0027s nice to have smaller, simpler configuration.\n\nAssuming that this approach holds up, I\u0027ll replicate it to our other projects.\n\nRELNOTES\u003dn/a\nPiperOrigin-RevId: 943469061\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0ba258051e8df6fe776108bd4faad4317ae2575f",
      "old_mode": 33188,
      "old_path": ".github/workflows/ci.yml",
      "new_id": "5447d87eeed7770d6dc0586effa531853b91aa9a",
      "new_mode": 33188,
      "new_path": ".github/workflows/ci.yml"
    }
  ]
}