Skip to content

Chore: Bump pinned GitHub Actions to Node.js 24 releases#74

Open
phranck wants to merge 1 commit into
mainfrom
issue/50-ci-node-24
Open

Chore: Bump pinned GitHub Actions to Node.js 24 releases#74
phranck wants to merge 1 commit into
mainfrom
issue/50-ci-node-24

Conversation

@phranck

@phranck phranck commented Jul 24, 2026

Copy link
Copy Markdown
Owner

Closes #50.

Summary

Bumps the three pinned GitHub Actions from their v4 Node.js 20 revisions to the current v5 Node.js 24 releases. All actions remain pinned by full commit SHA; only the referenced revisions and the adjacent version comments changed.

Action Before After
actions/checkout v4.3.1 (34e11487…) v5.1.0 (fbc6f399…)
actions/upload-artifact v4.6.2 (ea165f8d…) v5.0.0 (330a01c4…)
actions/download-artifact v4.3.0 (d3f86a10…) v5.0.0 (634f93cb…)

The v5 lines are the first Node.js 24-only releases of each action. Behavior (checkout options, artifact upload/download semantics, if-no-files-found: error gating) is preserved.

Test plan

  • scripts/validate-ci-configuration.sh passes (CI configuration remains deterministic)
  • actionlint reports no issues on .github/workflows/ci.yml
  • ./scripts/test-linux.sh green on macOS (Swift 6.0.3) and Linux (Docker 6.0.3-noble), warning-fatal
  • After merge: confirm the CI run produces no Node.js 20 deprecation annotations

- actions/checkout: v4.3.1 -> v5.1.0 (Node.js 24 runtime)
- actions/upload-artifact: v4.6.2 -> v5.0.0 (Node.js 24 runtime)
- actions/download-artifact: v4.3.0 -> v5.0.0 (Node.js 24 runtime)
- All actions stay pinned by full commit SHA; version comments updated
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.

[P2] Migrate GitHub Actions from Node.js 20 to Node.js 24

1 participant