Sonar Community Roundup; Jan 24 - 30, 2026

Sonar Updates
,
1

Hi all,

This week marks the release of the new SonarQube Server 2026.1 LTA! :tada: As always, we urge you to upgrade at your earliest convenience. Let us know here if you have any questions about it. And in case you’re wondering what an ‘LTA’ is.

And now, like every week, we’d like to take a moment to recognize you, the users, who help improve the ecosystem for everyone by sparking valuable discussions and providing feedback to drive continuous improvement in our products.

SonarQube for IDE:

SonarQube Server / SonarQube Community Build:

Rules & Languages Improvements:

  • An error raised by a dependency of the JavaScript / TypeScript sensor meant that some people’s pipelines started failing. It was first noticed on the Azure DevOps side by @groogiam, @zaat, @gsosa, @AlanChusuei, @Thamulansar, @hiteshgoldeneye, and @DesertDrifta, and then reported in a purely JavaScript context by @JW26. It was that latter report that finally allowed us to pinpoint and fix the problem. I’m afraid I’ve missed some people here in this list. Whether you’re listed here or not, we appreciate all the reports, context and most of all patience! This is fixed on SonarQube Cloud, in the newly released SonarQube server 2026.1 LTA and in the upcoming 26.2 SonarQube Community Build release.

  • @MisterPi found another rule where the “compliant” solution to one rule violates another rule. Thanks! SONARJAVA-5981

  • @JavierSA let us know about false positives from java:S3749 on uses of Lombok’s @RequiredArgsConstructor. It seems that our practice of filtering out issues when Lombok is involved is a little overly aggressive here. SONARJAVA-5980

  • null comparisons aren’t triggering csharpsquid:S2219. That’s because UnityEngine.Object overloads the == and != operators, so when compared with null it actually checks if the object was “destroyed” by the engine or not, instead of checking whether the actual reference is null. Thanks @Trisibo. We’re on it.

  • @Big-Iron-Cheems spotted a typo in kotlin:S6532. Thanks! We’ll get it fixed.

  • java:S6207 shouldn’t raise an issue when a constructor calls an overridden method from the same record, according to @pshem. We agree! SONARJAVA-5985

  • java:S2055 ignores annotations like Lombok’s @noArgsConstructor to raise an issue when a Serializable extends a class with no no-arg constructor. Thanks, @JackWhelpton. SONARJAVA-6003

  • @lukpsaxo pointed out that we hadn’t released the eslint-plugin-sonarjs npm plugin in 5 months. Oops. Fixed!

  • @lukpsaxo also let us know about a false positive from typescript:S2603 in a JSX context. We’ll fix it with JS-1173. Keep 'em coming!

  • @robabod let us know the code sample for java:S2301 is inappropriate. SONARJAVA-6007

  • After @duy.lam’s struggles to import coverage from an aggregate JaCoCo report, we’re going to improve performance with large, aggregate reports with JACOCO-70. In the meantime, though, he worked through the problem on his side and posted a demo project to help others. :heart_eyes:

  • @marc.free pointed out that web:S6836 doesn’t recognize Razor HTML helpers as form controls in labels. SONARHTML-345

  • @MisterPi doesn’t think the description of javascript:S1192 is clear enough about the exceptions to the rule and the interaction between the rule’s ignoreStrings parameter and built-in ignores. We’re on it!

  • java:S2637 doesn’t handle Lombok annotations well. This is actually something we struggle with across rules. Apparently it’s hard to analyze code that isn’t there. :sweat_smile: Nonetheless, we’re gonna try. JAVASE-162 Thanks @rhartinger!

  • @Ivy set up a custom rule based on the java:S3546 rule template. The point was to catch it when custom resources aren’t closed. Unfortunately that template has a bit of age on it and hasn’t been updated since the introduction of try-with-resources so they encountered false positives. We’ll fix it with JAVASE-163.

Thanks again to everyone mentioned here - and to anyone we may have missed - for your ongoing contributions in making this community stronger and helping us improve Sonar products.

If you’d like to give a shout-out to someone, whether a community member or a SonarSourcer who helped you, please do so below. And if there’s someone you think we should acknowledge next week, let us know!

 
Ann

3 Likes