SonarQube 10.4 released

Hi all,

Sonar is proud to announce the release of SonarQube 10.4, which displays the issues fixed by your Pull Request, the issues you accept, and much more. Details in the official announcement.

In addition, there are a few other items to note in the release:

  • We’ve updated the requirements to run the analysis of your code:
    In most cases, you now don’t need to install Node.js to analyze JavaScript, TypeScript, and CSS. When installing Node.js is still required, you need Node.js >= 16, or the analysis will fail.
    You also now need Java >= 17 and MSBuild >= 15.
  • Project overview gets a refresh, and as a result, the counters on the overall code of your projects will need to be recomputed. To display the missing counters, re-analyze your projects after the upgrade as described in the upgrade guide.
  • For faster analysis, you can enable the “Analyzers loading optimization” feature in the “General” settings of SonarQube. Scanners will only download the analyzers and 3rd-party plugins that are required for your project. Existing 3rd-party plugins may be incompatible and cause analysis errors with this feature enabled. This feature may currently introduce some limitations that we’ll track here as they are identified. Read more in this related community announcement.
  • We’ve started making the first endpoints of a new version of the Web API available. API v2 comes with dedicated documentation. Existing API v1 endpoints remain available and will gradually be deprecated as we replace them.

You’ll find more details in the upgrade notes and full details in the release notes. Please open new threads for any questions you have about these or other features.

As usual, download is available at Docker images are also available on Docker Hub.




A post was split to a new topic: SonarQube 10.4 requires more DB resources

A post was split to a new topic: SonarQube 10.4 breaks compatibility with the GitLab action