ci: bump actions to Node 24 (fix Node 20 deprecation) - #40
Merged
Merged
Conversation
actions/checkout, actions/setup-node and pnpm/action-setup v4 run on the deprecated Node.js 20 runtime. Bump them to v6 (node24) in both the release and CI workflows to silence the deprecation warning. Signed-off-by: Matteo Collina <hello@matteocollina.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
actions/checkout@v4,actions/setup-node@v4andpnpm/action-setup@v4run on the deprecated Node.js 20 runtime, which produces this warning on every run:Changes
Bumped all three actions to
@v6(which declareruns: using: node24) in:.github/workflows/release.yml(therelease-npmjob that surfaced the warning).github/workflows/ci.yml(same three actions, would show the identical warning on every push/PR)The release workflow logic is otherwise untouched — OIDC publishing (
id-token: write+--provenance, noNPM_TOKEN) already works.Notes
setup-node@v6keepscache: pnpmworking sincepnpm/action-setup@v6runs first in both workflows; the v6 caching behavior change only affects automatic npm caching, which we don't rely on.packageManager: pnpm@11.27.0is set in the rootpackage.json, so the pnpm setup step continues to resolve the version automatically.