Move the site workflow to Node 24 actions - #5
Merged
Merged
Conversation
actions/checkout and actions/setup-node v4 target the deprecated Node 20 runtime, which GitHub now forces onto Node 24 with a warning. v7 of both run on Node 24 natively. The workflow sets cache: npm explicitly, so the setup-node v5/v6 caching changes don't affect it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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.
Every site run warns that
actions/checkout@v4andactions/setup-node@v4target Node 20, which GitHub has deprecated, and forces them onto Node 24. This bumps both to v7, which run on Node 24 natively.cache: npmexplicitly, so that doesn't affect it.🤖 Generated with Claude Code