-
Notifications
You must be signed in to change notification settings - Fork 2.1k
ci: upgrade to Node.js 22 #10374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: upgrade to Node.js 22 #10374
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| "packageManager": "pnpm@8.14.0", | ||
| "engines": { | ||
| "node": "20.x" | ||
| "node": "22.x" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm upgrading the engines in package.json. I don't know if this is contentious or not. I'm seeing multiple versions of CI around the repository so I'm not sure if we consider this value important or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it turns out, we should definitely be doing this. This is now our source of truth.
Description
Upgrading our repository to Node.js 22 by reducing our source of truth to the value in
package.json#engines.Notably, this PR also adds Node.js 22 to the JS package test matrix.
Testing Instructions
CI