Repository navigation
Use Node 22 in CI and release workflows - #31
Open
mirzaaghazadeh wants to merge 1 commit into
Open
mirzaaghazadeh wants to merge 1 commit into
mirzaaghazadeh wants to merge 1 commit into
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.
Node.js 18 and 20 are end-of-life and received no fix in the October 21, 2026 Node.js security release (CVE-2026-111497 Brotli decoder RCE, CVE-2026-106069 / CVE-2026-105483 TLS hostname verification bypasses, CVE-2026-105482 DNS, and six more). This moves the setup-node version in CI to Node 22, whose 22.23.4 release carries those fixes. Only the Node version changes.