Bump Node.js from 20.20.0 (EOL) to 22.22.3 (Active LTS)#92137
Draft
mountiny wants to merge 1 commit into
Draft
Conversation
Node 20 reached end-of-life on April 30, 2026 and no longer receives security patches. Node 22 (codename Jod) is Active LTS until April 2027. Updates .nvmrc and package.json engines, which are the single source of truth fed to every workflow via the setupNode composite action. Co-authored-by: Cursor <cursoragent@cursor.com>
|
npm has a |
📲 Install BuildsAndroid
|
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.
Why
Node 20 reached end-of-life on April 30, 2026 and no longer receives security patches. We're currently running on an unsupported runtime in CI and in local development.
Node 22 (codename Jod) is the current Active LTS release, supported until April 2027. It's the conservative choice — Node 24 is newer and riskier for a large codebase.
What changed
.nvmrc:20.20.0→22.22.3package.jsonengines.node:20.20.0→22.22.3The
setupNodecomposite action reads.nvmrcvianode-version-file, so this single change propagates to every workflow automatically.Test plan
nvm install && nvm use && node --versionshowsv22.22.3npm installNo changes to application code.
.nvmrcandpackage.jsonengines only.Made with Cursor