Skip to content

ci: bump actions to v5 (Node.js 24 runtime)#459

Merged
Kamirus merged 1 commit intomasterfrom
chore/bump-actions-to-v5
Apr 27, 2026
Merged

ci: bump actions to v5 (Node.js 24 runtime)#459
Kamirus merged 1 commit intomasterfrom
chore/bump-actions-to-v5

Conversation

@ggreif
Copy link
Copy Markdown
Contributor

@ggreif ggreif commented Apr 27, 2026

Summary

GitHub Actions runners deprecate Node.js 20 (default switch June 2, 2026; removal September 16, 2026). The Tests workflow currently triggers a deprecation warning on every run because all three actions are pinned to Node-20-era SHAs. Example annotation on a recent run:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852…, actions/checkout@f43a0e5…, actions/setup-node@3235b87…. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026.

This PR bumps each to a release that ships with Node.js 24:

action from to
actions/checkout v3.6.0 (f43a0e5) v5.0.1 (93cb6ef)
actions/setup-node v3.9.1 (3235b87) v5.0.0 (a0853c2)
actions/cache v4.3.0 (0057852) v5.0.5 (27d5ce7)

Pins remain as full SHAs (with the human-readable version in a trailing comment) per the existing file style.

Test plan

  • CI passes (Tests workflow)
  • Deprecation warning on the run is gone
  • mops cache still hits across runs

🤖 Generated with Claude Code

GitHub Actions runners deprecate Node.js 20 (default switch June 2,
2026; removal Sept 16, 2026). Bump the three pinned actions in
tests.yml to versions that ship with Node.js 24:

- actions/checkout v3.6.0 → v5.0.1
- actions/setup-node v3.9.1 → v5.0.0
- actions/cache v4.3.0 → v5.0.5

Pins kept as full SHAs (with version comment) per the existing style.
@ggreif ggreif requested a review from a team as a code owner April 27, 2026 08:30
@Kamirus Kamirus merged commit 68e7479 into master Apr 27, 2026
4 checks passed
@Kamirus Kamirus deleted the chore/bump-actions-to-v5 branch April 27, 2026 13:04
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