Skip to content

ci: bump GitHub Actions to node24 runtimes - #315

Merged
PiTrem merged 2 commits into
masterfrom
chore/ci-bump-actions-node24
Jun 29, 2026
Merged

ci: bump GitHub Actions to node24 runtimes#315
PiTrem merged 2 commits into
masterfrom
chore/ci-bump-actions-node24

Conversation

@PiTrem

@PiTrem PiTrem commented Jun 29, 2026

Copy link
Copy Markdown
Member

What

Silences the "Node.js 20 is deprecated" warning on the Actions runner, and refreshes the pinned Node.

node24 action runtimes

Three actions still run on the node20 action runtime, which GitHub is deprecating in favour of node24. Bumped each to the major that runs on node24:

Action Bump Workflows
actions/checkout v4 → v5 testing, e2e, publish
actions/setup-node v4 → v5 testing, publish
cypress-io/github-action v6 → v7 e2e

Verified via each action.yml that @v6 Cypress is using: node20 while @v7 is node24. cypress-io/github-action@v7.0.0's only breaking change is that runtime bump, so the build / start / browser inputs are unaffected.

node-version

actions/setup-node's pinned Node bumped 22.17.1 → 22.23.1 (current latest 22.x) in testing + publish. Node 22 is in Maintenance LTS (supported to 2027-04-30), so this stays on a supported line and picks up security/critical fixes.

Not changed

  • Staying on the Node 22 line (Maintenance LTS) rather than moving to 24 (Active LTS) — minimal change; can revisit separately.
  • No engines field in package.json, so nothing to change there.

No application behaviour change — CI configuration only.

Note

This lands on master; the warning will persist on CI for branches that haven't picked it up yet (e.g. the in-flight 231-display-lcms-data stack) until it propagates down.

actions/checkout@v4, actions/setup-node@v4 and cypress-io/github-action@v6
all run on the node20 action runtime, which GitHub is deprecating — hence the
"Node.js 20 is deprecated" warning on the Actions runner. Bump each to the
major that runs on node24:

- actions/checkout       v4 -> v5   (testing, e2e, publish)
- actions/setup-node     v4 -> v5   (testing, publish)
- cypress-io/github-action v6 -> v7 (e2e)

This is the action runtime only; the build/test Node (node-version 22.17.1)
is unchanged. cypress-io/github-action v7.0.0's sole breaking change is the
node20 -> node24 runtime bump, so the build/start/browser inputs are
unaffected.
@PiTrem
PiTrem force-pushed the chore/ci-bump-actions-node24 branch from cb48520 to 892290f Compare June 29, 2026 10:54
@PiTrem PiTrem changed the title ci: bump checkout/setup-node to v5 (node24 runtime) ci: bump GitHub Actions to node24 runtimes Jun 29, 2026
The testing and publish workflows pinned Node 22.17.1; bump to the current
latest 22.x maintenance release (22.23.1). Node 22 is in Maintenance LTS
(supported to 2027-04-30), so this stays on a supported line and picks up
the security/critical fixes since 22.17.1.
@PiTrem
PiTrem merged commit d7148d9 into master Jun 29, 2026
2 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.

1 participant