SonarSource is thrilled to announce the release of SonarQube Server 2025 Release 1, the new LTA!
You’ll find a summary of all the new features added since the previous LTA in the official announcement. Check out the highlights to discover the great features we’ve worked on, including advanced AI capabilities, many security breakthroughs, enhanced developer experience, simplified operability, and many new language features.
In addition, there are a few other items to note since the last (10.8) release:
SonarQube Server now runs with Java 21 and on the recent versions of Kubernetes, including 1.32.
As before, to run the analysis, the scanner may auto-provision the JRE. When this is not the case, Java 17 LTS remains required. See more details in the scanner’s general requirements.
We’ve updated the list of supported DevOps platform versions, removing support for old versions. See more details in the documentation, such as for example in the documentation for GitHub.
You’ll find information about SonarQube Server 2025 Release 1 LTA in the release notes and details in the full release notes. If you’re upgrading from the previous LTA (9.9), you’ll find a consolidated version of the release notes in the LTA to LTA release notes.
If you’re upgrading across multiple versions, you should at a minimum read the upgrade notes for the intervening versions. If you’re upgrading from the previous LTA (9.9), you’ll find a consolidated version in the LTA to LTA upgrade notes. Also don’t forget that if you run a version older than the previous LTA (9.9), you need to upgrade to 9.9.8 first, and then to 2025 Release 1 LTA.
Please open new threads for any questions you have about these or other features.
Great news! With the new naming and versioning, I’m a bit confused about the upgrade path for our use case. We are on Server 10.8 Developer Edition and would like to keep our instance updated with the latest version, as we did till now.
Do we need / does it make sense for use to upgrade to 2025 Release 1 LTA?
What will be the versioning schema going forward? Are you moving away from semantic versioning the releases?
Seems lightly confusing with respect to the major vs minor nomenclature.
Just to confirm, does this mean that all LTA fix releases going forward will be 2025.1.x for patches to the LTA? And anything starting with 2025.2 forward is the the release line for the next LTA which will eventually be 2026.1??
I’m a little but confused about this new LTA release. Is it avaiable for community editions?
I can only see a tag sonarqube:lts-community, that if I’m not mistaken brings the 9.9.8 version.
I can also see several 2025-lta-*** tags, but they seem to be only for enterprise and above servers.
If I pull from tag 25.1.0.102122-community, would this be a LTA version? Or would it keep asking for updates very frequently?
SonarQube Server and SonarQube Community Build are now separate products with different versioning and release cadences. And there is no LTA for SonarQube Community Build. Explicitly, that means there will be no patches for Community Build; to get fixes, you’ll need to upgrade.
Hi Ann!
Thanks for the quick response and the clarification.
Would you happen to know how long until a community build is no longer active or not supported? For example, if I take 25.1.0.102122-community, when will this no longer be feasable?
So just to double check, the latest LTA for community build would be 9.9.8?
I was trying to find out if i would need to update from 10.8.1 to “something 2025” to keep the “non-LTA” SQ-Enterprise-Instance “active” and “updateable” for the “fast release cadence” (e.g. 10.6/10.7/10.8…)
I currently am unsure if i get your message straight:
So the 2025.1 IS both an LTA and the current “next interims release” of the faster release cadence?
So i would transition from 10.8.1 to 2025.1 and in ~2 month there comes along 2025.2 and i can install that?
It would feel right, that way. But i have no clue if i got that right
Please be so kind and enhance these docs with the new versioning scheme, too!
It’s SonarQube Community Build that now has “the faster release cadence”. SonarQube Community Build versioning now looks like YY.m, i.e. 2-digit year and month.
SonarQube Server is versioned like YYYY.n, i.e. 4-digit year and increment.
So yes, 2025.1 is currently both the LTA and the latest SQS release. It is not the “next interims(sic) release”.
Yes
Yes and no. The two months are almost up; 2025.2 will be released in March.
)
