Drop Node.js v18 support in analysis environment

Sonar Updates
, , ,
1

Hi everyone,

SonarQube analysis environment uses Node.js to support JavaScript, TypeScript, HTML, CSS, and YAML. See the docs for details.

What is going on?

Node.js v18 is no longer supported in the analysis environment.

It will no longer work starting from SonarQube Server 2025.5 and it does not work in SonarQube Cloud since the start of this week.

Affected users had a deprecation warning in the UI and analysis logs since November 2024.

Am I affected?

Most users are not concerned, since the runtime is built-in with SonarQube in most environments.

You are affected if, in your analysis environment, any of these is true:

  • You have set analysis parameters that override the embedded runtime
  • You use a processor architecture we don’t support for the built-in Node.js
  • You are using an outdated version of glibc or musl in docker images or Linux distro
  • You have a deprecation warning about Node.js v18 since November 2024

What to do?

In the unlikely case you are affected (see above), your analysis will fail and you will need to upgrade the runtime in your pipeline or remove any overriding parameter you had set.

If you need to upgrade Node.js, we recommend the latest LTS version.

Note that this does not affect anything outside your analysis environment.