chore(ci): upgrade node to 22 lts (test on 22 and 24)#2433
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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 18 (EOL April 2025) and Node 20 (out of maintenance April 2026) are unsupported upstream. This brings CI onto supported LTS lines and declares the floor in the root
package.json.Changes
Build,Test:unit,Test:types,Test:E2E) now run on22.xand24.xpublish-ciandare-the-types-wrongmatrices moved from18.xto22.xnightly,checks,bundle-size,experimental) read Node from.nvmrcinstead of hard-coding20.nvmrcrefreshed to22.22.3(latest 22.x patch)package.jsondeclares"engines": { "node": ">=22" }. Scoped to root only — published packages underpackages/*andtargets/*are untouched, so library consumers see no change.Notes
enginesis intentionally root-only. If we want to declare a floor for consumers in future, that's a separate SemVer-relevant call.pnpm install --frozen-lockfile,pnpm build-ci,pnpm test,pnpm docs:buildall clean.