-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Make Node.JS v22 the new target version #32068
Comments
What does that mean specifically? Eg do we drop support for 20? Some CI/CD systems may not have 22 support for a while. |
Basically yes, we drop official support for v20. That being said it will still run, with a warning in the logs.
Shouldn't be a problem as v22 is already out for months. |
I think we enforce nice version today don't we? |
This is causing my self-hosted renovate CI job to fail: [2024-10-31T00:34:11.526Z] INFO: Renovate is exiting with a non-zero code due to the following logged errors
[2024-10-31T00:34:11.526Z] "loggerErrors": [
[2024-10-31T00:34:11.526Z] {
[2024-10-31T00:34:11.526Z] "name": "renovate",
[2024-10-31T00:34:11.526Z] "level": 50,
[2024-10-31T00:34:11.526Z] "logContext": "pjpoOl8NkY0_X5Pz-KnAG",
[2024-10-31T00:34:11.526Z] "versions": {
[2024-10-31T00:34:11.526Z] "node": "22.11.0",
... omitted for brevity
[2024-10-31T00:34:11.526Z] },
[2024-10-31T00:34:11.526Z] "range": "^20.15.1",
[2024-10-31T00:34:11.526Z] "msg": "Unsupported node environment detected. Please update your node version."
[2024-10-31T00:34:11.526Z] }
[2024-10-31T00:34:11.526Z] ]
...
[2024-10-31T00:12:48.735Z] "renovateVersion": "38.138.4" |
No it's not |
That's a little disingenuous. Renovate completes "successfully" but the CI job does fail because Renovate exits with a non-zero exit code |
You are:
|
Updates Renovate's package.json>engines to add support for Node v22 LTS, and updates Renovate official Docker images to run on Node v22 instead of Node v20. Closes #32068 BREAKING CHANGE: Renovate Docker images will now be based on Node.js v22 instead of v20
🎉 This issue has been resolved in version 39.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
With the release of Node.JS v23 we are getting officially v22 as LTS.
We should use it as default target, so we keep getting back ported features.
https://nodejs.org/en/about/previous-releases
The text was updated successfully, but these errors were encountered: