Make Node.JS v22 the new target version

[secustor]

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

[rarkins]

What does that mean specifically? Eg do we drop support for 20? Some CI/CD systems may not have 22 support for a while.

[secustor]

Basically yes, we drop official support for v20. That being said it will still run, with a warning in the logs.

Some CI/CD systems mayr not have 22 support for a while.

Shouldn't be a problem as v22 is already out for months.

[rarkins]

I think we enforce nice version today don't we?

[viceice]

At least we should support node 22. It's scheduled for LTS in two days¹. We currently only support v22

renovate/package.json

Line 138 in c7d66d1

"node": "^20.15.1",

Footnotes

1. https://github.com/nodejs/Release?tab=readme-ov-file#release-schedule ↩

[maccuaa]

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"

[rarkins]

No it's not

[maccuaa]

That's a little disingenuous. Renovate completes "successfully" but the CI job does fail because Renovate exits with a non-zero exit code

[rarkins]

You are:

• Mistakenly using Node 22 when Renovate currently supports Node 20 only, which caused your error, and
• Wasting our time in an issue where we are planning to make Node 22 the default for our Docker images (which apparently you are not using, because if you did then you wouldn't have the problem)

[renovate-release]

🎉 This issue has been resolved in version 39.0.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 39.0.0

Your semantic-release bot 📦🚀