SonarQube Server 2025 Release 4.1

SonarQube Server / Community Build Releases
1

Hi all,

Sonar is excited to announce the release of the SonarQube Server 2025 Release 4(.1).

This version brings SAST for Go, expanded secrets detection, many new rules for Python coroutines and comprehensions, Java 23/24 and Java performance, and much more. We’ve enhanced SonarQube Advanced Security with continuous vulnerability detection without reanalysis, alongside PHP dependency support, dependency risks displayed right in your IDE for comprehensive protection. Enjoy these and many other exciting features in this release.

Details are in the official announcement and the Release Notes (and full release notes in Jira). For upgrade instructions, refer to the upgrade notes.

As usual, downloads are available at sonarsource.com. Docker images are available on Docker Hub and Helm charts are available on ArtifactHub.

Due to an issue identified in the initial release, please use 2025 Release 4.1. More details on the issue here.
Ready to dive in? Check out SonarQube 2025 Release 4.1!

Elena & Chris

1 Like
2

Hello,
I just upgraded a small DE instance from 2025.3.1 to 2025.4.1, and all projects now show that the main branch is empty (on the main SonarQube page). If I click on any project, I can see data from all branches (main branches and pull requests). Executing an analysis on the main branch of any project doesn’t change anything. Is that a known issue in this version ?
Just for the context and in case that changes anything, I upgraded to 2025.4 first (as I didn’t see this message), and got hit by the license problem and the empty main branch problem. I then upgraded to 2025.4.1, the license problem was fixed but not the empty main branch problem. I then restored the 2025.3.1 database backup, downgraded SQ to 2025.3.1, restarted SQ instance without any issue, then upgraded directly to 2025.4.1 with the same issue.
Gilles

3

Thanks for bringing this to our attention. This is a new issue for us, and we don’t yet know what’s causing it in your case.

4

Tried again this morning, issue can still be reproduced. Didn’t find anything in the logs. I can share the database with the support team if you’re interested.

6

I had the same issue of projects (the main branch of this project is empty) after upgrading to 4.1
We use local projects with key, had to rollback

Edition - Developer

image
image913×179 12.1 KB

7

Thanks for sharing this.
Have you tried forcing an Elasticsearch reindex after the upgrade? That might resolve the issue. Here are the docs for it: Forcing Elasticsearch reindex

8

I did, but that didn’t change anything.

9

Hi,

I am running a SonarQube DE. I upgraded the instance from 2025.3 to 2025.4.1 this morning, and I am facing the same issue.
I forced an Elasticsearch reindex, but the issue still persists.

10

Hi,

The same as others here, upgraded to 2025.4.1, forced reindex and my projects are still showing as “The main branch of this project is empty”.

11

Hello,

we have the same problem. Even a new analysis of the projects does not restore the status in the overview.

12

Hey @gquerret , @PaulAnand , @JCradock , @progs

Thanks for the reports. Can you let me know which mode your instances use? Standard or MQR?

13

@Colin My instance uses standard mode.

14

My server is on MQR mode.

15

Mine is on MQR mode.

16

MQR too

image

17

Thanks team.

Finally, the mode didn’t matter.

Thanks to @gquerret for getting us a database that reproduces the issue, we found that the issue affects instances that don’t have access to SonarQube Advanced Security. Still testing to see if this only affects Developer Edition, or other editions as well.

Update: We now know that it only affects Developer Edition.

Of course, we know now that we have an issue to fix. I’m sure a ticket will be created soon and a new release. Right now, we don’t have a workaround.

2 Likes
18

I also see the same issue after upgrading to 2025 Release 4.1. Do you know when a Fix will be released for this issue?

20

I don’t have an ETA. I would really hope by the end of this week :crossed_fingers: We’ll keep you posted.

1 Like
21

2025.4.2 should be released very soon.

1 Like
22

Thanks, version 2025.4.2 resolved a similar problem in our environment.