Repository navigation
ci: install the latest Node 22 patch in setup-node - #131
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
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.
What & why
Astro 7.4.2 requires Node >=22.23.4, but the runner's tool cache still has 22.23.3 and
setup-nodeused it becausecheck-latestwas off, so the build in #130 failed.Changes
check-latest: trueon the threesetup-nodesteps (ci.yml×2,deploy.yml).engines.noderaised to>=22.23.4inpackage.jsonand the lockfile root.Testing
npm run lint,npm test(22 passed) andnpm run buildlocally on Node 22.23.2 with Astro 7.4.0. The Node 22.23.4 install is checked by this PR's own CI run.