Skip to content

ci(ENG-3243): move action pins off the deprecated Node 20 runtime - #51

Merged
elgordomac merged 1 commit into
mainfrom
gordon/eng-3243-node20-action-pins
Oct 9, 2026
Merged

elgordomac merged 1 commit into
mainfrom
gordon/eng-3243-node20-action-pins

Conversation

@elgordomac

@elgordomac elgordomac commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

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_TEMP instead of .git/config; git commands 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/checkout bumps v4 → v6.0.2. The only change that matters here is that persisted credentials now live under $RUNNER_TEMP instead of .git/config; no workflow pushes in a way that depends on the old location.
  • googleapis/release-please-action bumps 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.

Written for commit 37a4669. Summary will update on new commits.

View guided diff Turn on auto-fix

Swap every JavaScript action that still declares the node20 (or older)
runtime for a release that declares node24, keeping this repo's pin
style. Workflows that push take checkout v5 rather than v6, so their
credential handling is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 8, 2026 12:39

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Both SHAs match the stated releases, use Node.js 24, and preserve the required workflow inputs.

0 open findings

What changed in this PR

Updates workflow actions from deprecated Node.js 20 runtimes to Node.js 24.

Changes:

  • Upgrades actions/checkout to v6.0.2.
  • Upgrades release-please-action to v5.0.0.
  • Retains immutable SHA pinning.
File Description
.github/​workflows/​validate.yml Updates checkout to Node.js 24-compatible v6.0.2.
.github/​workflows/​release-please.yml Updates release-please to Node.js 24-compatible v5.0.0.

🧠 Review effort: Balanced


Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Auto-approved: Bumps the two GitHub Actions pins (checkout v4→v6, release-please v4→v5) to the Node 24 runtime; a workflow-only, bounded tooling update that clears deprecation annotations and is easily reversible.

View guided diff | Turn on auto-fix | Re-trigger cubic

@elgordomac
elgordomac merged commit 19b9dde into main Oct 9, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants