ci(ENG-3243): move action pins off the deprecated Node 20 runtime
Summary
Moves every JavaScript action in this repo's workflows that declares the Node 20 (or older) runtime to a release that runs on Node 24, removing the "Node.js 20 is deprecated" annotations GitHub adds to every job that uses one. Part of ENG-3243, which has done the same across the org.
| Action | From | To | Pins |
|---|---|---|---|
actions/checkout | v4 | v6.0.2 (de0fac2) | 1 |
googleapis/release-please-action | v4.4.1 | v5.0.0 (45996ed) | 1 |
Compatibility
- checkout v6 stores the persisted credential under
$RUNNER_TEMPinstead of.git/config;gitcommands keep working. No workflow here pushes or runs in a container job. - release-please v5 only moves to Node 24.
- The remaining bumps are same-major or majors whose only breaking change is Node 24 itself. All need runner v2.327.1+, which GitHub-hosted and WarpBuild runners already meet.
Testing
Workflow-only change. Steps that only run on push, release, deploy or schedule aren't exercised by this PR's CI and will first run on merge.
🤖 Generated with Claude Code
Summary by cubic
Moves this repo's two JavaScript workflow actions off the deprecated Node 20 runtime, removing the "Node.js 20 is deprecated" annotations GitHub adds to every job that uses them.
actions/checkoutbumps v4 → v6.0.2. The only change that matters here is that persisted credentials now live under$RUNNER_TEMPinstead of.git/config; no workflow pushes in a way that depends on the old location.googleapis/release-please-actionbumps v4.4.1 → v5.0.0, which only changes the runtime.
Workflow-only change: steps that only run on push, release, deploy, or schedule aren't exercised by this PR's CI and will first run on merge.