ci: move Node 20 actions to their Node 24 majors - #1183
Merged
Merged
Conversation
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
2 participants
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.
Fixes #1179
Runners warn that these actions target the deprecated Node.js 20 runtime. Each is bumped to its current major, all of which declare
runs.using: node24:Checked the breaking changes. setup-node v5 turned on automatic caching, and v6 narrowed it to npm only; this repo uses pnpm. setup-node v7 dropped the
NODE_AUTH_TOKENexport, and no workflow here usesregistry-url. The pnpm/action-setup v6 inputs still includeversion.docs-release.yml(deploy-pages, upload-pages-artifact) only runs on push to main, so CI on this PR does not exercise it. The first run after merge does.Workflow-only change; no e2e scope touched.