SonarQube Community Build 25.12.0.117093 released

SonarQube Server / Community Build Releases
1

Hi all,

Sonar is excited to announce the availability of the SonarQube Community Build 25.12.0.117093, our December release.

This version introduces several enhancements, including new rules for Python 3.14, CCS accessibility rules, and a refreshed look for the login page.

Details are in the Release Notes. You’ll find all fixed tickets in the full release notes. Please open new threads for any questions you have about these or other features.

As a reminder, running SonarQube Community Build with Java 17 is deprecated and in future versions using Java 21 or above will be required. Using Java 17 for SonarQube scanners on the machine running the analysis is now also deprecated, the auto-provisioned JRE has changed to Java 21, please find more information here.

As usual, download is available at SonarSource.com. Docker image will be available shortly on Docker Hub. You can find on Artifact Hub how to use the latest SonarQube Community Build with the official Helm chart.

Elena

2

Hi team,

We’re facing an upgrade blocker on SonarQube Community Build 25.12.0.117093 when running on Azure SQL.

Environment:

  • SonarQube: Community Build 25.12.0.117093
  • Deployment: Azure App Service (container-based)
  • Database: Azure SQL
  • DB collation: SQL_Latin1_General_CP1_CS_AS (as required)

Issue:
During startup, SonarQube correctly connects to the database, but fails during the manual DB migration step (/setup).

Error:
Migration step #202506016 fails:
“Add index based on ‘resource_id’ and ‘resource_type’ to ‘jira_work_items_resources’ table”

Root error:
Cannot resolve collation conflict between
SQL_Latin1_General_CP1_CI_AS and SQL_Latin1_General_CP1_CS_AS
occurring in UNION ALL operator during metadata/index lookup.

Observations:

  • DB connection works (HikariPool initialized successfully)
  • Failure occurs when SonarQube queries index metadata
  • Looks like a mixed collation issue triggered by the migration logic itself

Question:
Is this a known issue with 25.12.x on SQL Server/Azure SQL?
Is there a recommended workaround other than rebuilding the database?

Thanks!

3

We got the same Problem with 2025.6. We solved it by downgrading the driver back to 13.2.0

7

Hi team,

I’m wondering why there is a release without a corresponding tag/release in the github repo. Are these no longer available?

Thanks!

8

We had a few issues that were not stopping the release of SQCB 25.12, but that were not allowing us to create a tag to a buildable commit on the public repo.
The issues have been fixed and the tag will be available on GitHub in the next hours.

3 Likes
9

As promised, we managed to add the release/tag to the GitHub repo:

We will make sure to avoid this delay once 26.1 gets released in January!

2 Likes