chore: Downgrade node.js version to 22#3176
Open
filzrev wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
I'm not sure why cached Node.js version is used on some CI executions. On latest CI executions. It seems Though, It's better to use Node.js |
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.
On recent GitHub Actions runner images.
Setup Additional Toolsfailed.It seems cached Node.js version
24.16.0is used and explicitly specified24.15.0version seems ignored in some cases.This PR downgrade Node.js version to
22.xtemporary.Because Node 22 is not affected by #3154. and it can receive security updates.