Repository navigation
Update checkout and setup-node to v7 for Node 24 - #61
Merged
Merged
Conversation
GitHub has deprecated Node 20 for actions and warns on every run that actions/checkout@v4 and actions/setup-node@v4 are being forced onto Node 24. v7 of both target Node 24. Both workflows already set cache: 'npm' and package.json has no packageManager field, so setup-node's caching changes since v5 don't apply.
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
Every CI run warns: Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. This bumps both to v7, which target Node 24, in
node.js.yml(CI) andgithub-pages.yml(deploy).Breaking changes checked (v5–v7 release notes):
package.jsonhas apackageManagerfield. There isn't one, and both workflows setcache: 'npm'explicitly, so caching is unchanged.NODE_AUTH_TOKEN. That only matters for publishing to npm, which neither workflow does.Testing
This PR's CI run uses the new versions.
github-pages.ymlonly runs on pushes tomaster, so the deploy workflow will first run with v7 after merge.🤖 Generated with Claude Code
https://claude.ai/code/session_01FJAB1xUz2Ks7btZ9WRyMgh