refactor: use latest node version #149
Merged
Conversation
This file contains 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.
This PR enables the
check-latestoption for all action/setup-node steps, which ensures that the latest Node version is used that satisfies the version spec.I.e. whenever we're using a version like
22,22.xorlts/*it'll ensure we're using 22.12.0 (at time of writing).This avoids an old cached version from being used in actions.
See https://github.com/actions/setup-node?tab=readme-ov-file#usage
We'll want this to get 22.13.0 when it becomes available to fix nodejs/node#56137, which is currently plaguing our CI jobs across most repos, otherwise we may still be using a cached version of 22.12.0.
Checklist
and the Code of conduct