Release notes
The release notes describe the relevant changes implemented for each SonarQube Community Build release.
For a complete list of all changes, see Full release notes.
SonarQube Community Build 26.10.0.133078 and earlier trust compromised eMudhra certificate authorities. To protect your installation, update to version 26.11.0.134175.
New and enhanced features
View the release notes for new and enhanced features for SonarQube Community Build.
Latest release - 26.11.0.134175
Languages
HTML
A new accessibility rule flags the scope attribute on elements other than table headers, and alternative text checks now cover inline SVG elements. False positives have been reduced on duplicate IDs in mutually exclusive Angular and Vue template branches.
S9380: The "scope" attribute should only be used on "th" elements
Improvements have been made to the following rules:
S1077: Image, area and button with image elements should have an "alt" attribute
S7930: HTML elements should have unique "id" attribute values
For more information about this language analysis, see HTML.
IaC (Infrastructure as Code)
Terraform versions 1.3 to 1.16 are now supported. Terraform analysis now recognizes Terraform actions (action blocks and lifecycle.action_trigger) and provider-defined functions (provider::<name>::<function>), and existing checks now also apply to import, check, removed, moved, and ephemeral blocks. False positives have been reduced in Terraform on S3 buckets used as server access logging destinations. Improvements have been made to the following rule:
S6258: Cloud resources logging should not be disabled (Terraform)
For more information about this language analysis, see Terraform.
Java
The following new rules have been added:
S9412: "Collections.sort()" should not be used
S9413: Redundant "String.format" should be removed when native formatting is available
S9427: Java assert statements should not be used in test code
S9428: MessageDigest instances should not be stored as fields
S9433: Literals should not be converted to strings using empty string concatenation
S9434: Qualified "this" should not be used when the unqualified form is enough
S9435: Ternary operator conditions should not be negated
S9436: Classes should not declare more than one logger
S9437: "getInstance()" methods should not return a new instance on every call
S9438: Private fields that are never reassigned after construction should be declared "final"
S9439: Array initializers should use the shorthand form instead of an explicit "new" array creation
Spring bean analysis now covers projects with several modules, and @Profile expressions that use the !, &, and | operators are supported. False positives and false negatives have been reduced across several rules. Improvements have been made to the following rules:
S2077: SQL queries should not be dynamically formatted
S2245: Pseudorandom number generators (PRNGs) should not be used in security contexts
S4605: Spring beans should be considered by "@ComponentScan"
S4790: Weak hashing algorithms should not be used
S5128: "Bean Validation" (JSR 380) should be properly configured
S7158: "String.isEmpty()" and "String.isBlank()" should be used to test for emptiness and blankness
S9352: Bean autowiring ambiguity should be resolved using "@Qualifier" or "@Primary"
The following rules have been added to the Sonar way quality profiles:
S1314: Octal values should not be used
S1695: "NullPointerException" should not be explicitly thrown
The following rule has been removed from the Sonar way quality profiles:
S9397: "String.format()" should not be used when simpler alternatives exist
For more information about this language analysis, see Java.
JavaScript, TypeScript, CSS
New CSS rules for property validity, font loading, and motion accessibility have been added:
S9423: "!important" should not be used
S9424: CSS property values should be valid
S9440: Spatial motion should respect reduced-motion preferences
S9441: Downloadable text fonts should use a non-blocking "font-display" strategy
S9449: Transitions should name the properties they animate
Alternative text checks now cover inline SVG elements in JSX and TSX, and false positives have been reduced across several rules. Improvements have been made to the following rules:
S1077: Image, area, button with image, object and svg elements should have an alternative text
S1101: Links with identical accessible names should have identical targets
S1848: Objects should not be created to be dropped immediately without being used
S2234: Parameters should be passed in the correct order
S2245: Pseudorandom number generators (PRNGs) should not be used in security contexts
S2699: Tests should include assertions
S6523: Optional chaining should not be used if returning "undefined" throws an error
S6747: JSX elements should not use unknown properties and attributes
S6772: Spacing between inline elements should be explicit
S6827: Anchors should contain accessible content
S6845: Non-interactive DOM elements should not have the
tabindexattributeS6850: Heading elements should have accessible content
S7059: Constructors should not contain asynchronous operations
S7652: Output bindings should not be named "on" or prefixed with "on"
S7653: Output bindings should not be aliased
S7739: Objects should not have a "then" property
S7767: Bitwise operators should not be used to truncate numbers
For more information about this language analysis, see JavaScript, TypeScript, CSS.
Kotlin
Kotlin 2.4.21 is now supported, and false positives have been reduced on the names of test functions. Improvements have been made to the following rule:
S100: Function names should comply with a naming convention
For more information about this language analysis, see Kotlin.
PHP
False positives have been reduced across several rules. Improvements have been made to the following rules:
S1068: Unused "private" fields should be removed
S1186: Methods should not be empty
S1313: IP addresses should not be hardcoded
S1481: Unused local variables should be removed
For more information about this language analysis, see PHP.
Secrets
GitHub App installation tokens in the JWT-based format are now detected, and false positives have been reduced on quoted database passwords. The following rules are affected:
S6689: GitHub tokens should not be disclosed
S6703: Database passwords should not be disclosed
For more information about this language analysis, see Secrets.
API
New v2 endpoint to get projects
The new GET /api/v2/components/projects endpoint returns the projects you have Browse permission on, by project ID or key. You can narrow the results with more filters, including tags, and set pageSize to 0 to get only the number of matching projects.
Also see Web API.
Administration
Clearer pending task age on the Background tasks page
On the Background tasks page, the pending time value has a clearer label, and its tooltip now explains that the value is how long the oldest pending task has been waiting, not an estimate of the time left to process the queue.
Database latency metric
The api/monitoring/metrics endpoint now reports sonarqube_db_latency_seconds, the round-trip time of the database validation query, excluding the time spent waiting for a pooled connection. Use it to tell network latency between SonarQube Community Build and its database apart from slow queries.
Previous releases
Version 26.10.0.133078
Quality profiles
Three built-in Sonar way quality profiles
SonarQube Community Build now provides three built-in quality profiles for each language, so you can choose how strict your analysis is. Sonar way core activates the same security rules as the other two profiles and the most impactful reliability and maintainability rules. Sonar way extended adds more reliability and maintainability rules. Sonar way comprehensive activates all recommended rules. On new installations, Sonar way core is the default profile for each language.
Also see Built-in quality profiles.
Languages
Go
A new rule flags code that shadows predeclared identifiers, and false positives have been reduced on string literals used in HTTP routes.
S978: Predeclared identifiers should not be shadowed
Improvements have been made to the following rule:
S1192: String literals should not be duplicated
For more information about this language analysis, see Go.
HTML
A new accessibility rule flags the use of the autofocus attribute, and false positives have been reduced on component tags and in ASP.NET WebForms, Razor, Angular Material, and Vue templates.
S9379: DOM elements should not use the "autofocus" attribute
Improvements have been made to the following rules:
S1082: Mouse events should have corresponding keyboard events
S1097: "input", "select" and "textarea" tags should be labeled
S5256: Tables should have headers
S7930: HTML elements should have unique "id" attribute values
The following rules have been removed from the Sonar way quality profiles:
S4084: Videos should have subtitles
S5257: HTML "<table>" should not be used for layout purposes
For more information about this language analysis, see HTML.
IaC (Infrastructure as Code)
Docker analysis now covers Containerfiles in addition to Dockerfiles. Syntax highlighting no longer fails on certain Azure Resource Manager JSON files, and JSON files generated from Bicep are no longer analyzed unless you include them explicitly. False positives have been reduced in Azure Resource Manager and Docker. Improvements have been made to the following rules:
S117: Parameter and variable names should comply with a naming convention (Azure Resource Manager)
S1192: String literals should not be duplicated (Azure Resource Manager)
S1481: Unused local variables should be removed (Azure Resource Manager)
S6504: Sensitive resources copied to Docker images should not be owned or writable by non-root users (Docker)
S6954: Elements should not be empty or null (Azure Resource Manager)
S6975: The resource elements should appear in the recommended order (Azure Resource Manager)
S8431: Specify either version tag or digest for image (Docker)
For more information about these language analyses, see Azure Resource Manager, CloudFormation, Docker, Kubernetes/Helm, and Terraform.
Java
The following new rules have been added, covering TestNG, collections and streams, numeric conversions, concurrency, and date and time handling:
S3037: Record component accessors should not be called before the fields are assigned
S3949: Calculations should not overflow
S9366: Duration conversions should agree with the supplied TimeUnit
S9386: Float literals should be used instead of casting double literals to float
S9387: TestNG Javadoc tags should be converted to annotations
S9388: TestNG data provider methods should return valid types
S9389: Data provider names should be unique within a class
S9390: Manual null checks should be replaced with "Objects.equals()"
S9391: Loops should use Stream API when performing filter, map, or collect operations
S9392: Redundant range checks should be removed
S9393: "Duration.get()" should only be called with SECONDS or NANOS
S9394: "contentEquals()" should be used instead of "equals()" for "CharSequence" comparisons
S9395: Numeric values should be explicitly cast when assigned to narrower types
S9396: Inner class fields should not shadow outer class fields
S9397: "String.format()" should not be used when simpler alternatives exist
S9398: Inner classes should not be declared inside interfaces
S9399: Instance fields should not be guarded by static locks
S9400: Method references not fulfilling the "Comparator" contract should not be used as comparators
S9401: IdentityHashMap keys should not be boxed primitive types
S9402: Sorted collections should have an ordering for their element or key types
S9403: "Arrays.fill()" should not be called with an incompatible value type
S9404: "Optional" should not wrap collections, maps, or arrays
S9411: Loops that transform list elements should use "List.replaceAll()"
Rule S4426 (Cryptographic keys should be robust) can now be configured. False positives and false negatives have been reduced across Spring, JUnit 5, and Mockito code. Improvements have been made to the following rules:
S1602: Lambdas containing only one statement should not nest this statement in a block
S2123: Values should not be uselessly incremented
S2229: Methods should not call same-class methods with incompatible "@Transactional" values
S2479: Whitespace and control characters in literals should be explicit
S2699: Tests should include assertions
S5786: JUnit5 test methods should have default package visibility
S5810: JUnit5 test classes and methods should not be silently ignored
S6832: Non-singleton Spring beans should not be injected into singleton beans
S8924: Mockito core methods should be statically imported
S8989: Methods with "@Transactional" should specify rollback behavior for checked exceptions
S9133: Predefined mathematical constants should be used instead of hard-coded approximations
S9148: "Float.compare" or "Double.compare" should be used for floating-point comparisons
S9342: Archive entries should not be empty
S9351: "BigDecimal.compareTo()" should be used instead of "equals()" for numerical comparison
For more information about this language analysis, see Java.
JavaScript, TypeScript, CSS
New rules for promises, asynchronous code, and accessibility have been added:
S7503: Async functions should use async features
S9379: DOM elements should not use the "autofocus" attribute
S9380: The "scope" attribute should only be used on "th" elements
S9381: Promises should not be nested
S9382: Promises should not be awaited sequentially in a loop
S9383: Promises should not be left unhandled
False positives have been reduced across several rules. Improvements have been made to the following rules:
S107: Functions should not have too many parameters
S1128: Unnecessary imports should be removed
S1848: Objects should not be created to be dropped immediately without being used
S2187: Test files should contain at least one test case
S2819: Origins should be verified during cross-origin communications
S4123: "await" should only be used with promises
S5332: Clear-text protocols should not be used
S7739: Objects should not have a "then" property
S9145: Vue components should not use the deprecated "vue-class-component" or "vue-property-decorator" libraries
For more information about this language analysis, see JavaScript, TypeScript, CSS.
Kotlin
False positives have been reduced across several rules. Improvements have been made to the following rules:
S100: Function names should comply with a naming convention
S1133: Deprecated code should be removed
S1192: String literals should not be duplicated
S1874: Code annotated as deprecated should not be used
S5332: Clear-text protocols should not be used
S6518: Element access should use indexed access operators
S6615: Variables assigned values should be read
S6619: Null checks should be useful
For more information about this language analysis, see Kotlin.
PHP
False positives have been reduced across several rules, including on Laravel code and in test files. Improvements have been made to the following rules:
S1124: Modifiers should be declared in the correct order
S1172: Unused function parameters should be removed
S1313: IP addresses should not be hardcoded
S3011: Reflection should not be used to increase accessibility of classes, methods, or fields
S4144: Methods should not have identical implementations
For more information about this language analysis, see PHP.
Scala
SonarQube Community Build imports ScalaTest test execution reports and Scalafix findings for Scala projects.
For more information about this language analysis, see Scala.
API
Request parameter validation in v2 web API endpoints
The v2 web API endpoints now validate the names of the request parameters they receive, so a misspelled or unsupported parameter is reported instead of being silently ignored.
Response content type in the web API documentation
The web API documentation now shows the content type of each endpoint's response.
Also see Web API.
Administration
Project coverage
Project coverage shows whether every repository in your organization is connected, imported, and actually being scanned. Close any gaps by working through three steps: connect a DevOps platform, import your repositories, and get your projects analyzed. Go to Administration > Project coverage to see a progress chart for each step, a coverage timeline tracking projects analyzed and repositories imported over time, and a full project list you can search, filter, and act on individually. Viewing the page requires the Administer System permission, and importing repositories or configuring a project from it also requires the Create Projects permission.
Also see Project coverage.
Masking detected secret values in source code
SonarQube Community Build can hide the value of a detected secret instead of showing it in plain text. The Mask detected secret values in source code setting (sonar.security.secretSourceRedaction.enabled) is disabled by default. Enable it to mask secret values in the source code view and in web API responses that return source code, and where a safe location cannot be determined within a file, the whole source of that file is masked instead. The findings themselves stay visible, keeping their locations and descriptions. The setting takes effect immediately, with no reanalysis or restart. To turn it on, go to Administration > Configuration > General settings > Security.
Also see Masking detected secrets in source code.
Configurable SMTP OAuth scope
The OAuth scope that SonarQube Community Build requests when it authenticates to an SMTP server is now configurable, which allows email notifications to work with providers that expect a scope other than the default.
Also see Notifications.
Deployment
Tomcat access log written to standard output
The Tomcat access log can now be written to standard output, so containerized deployments can collect it with the rest of the SonarQube Community Build logs. Set sonar.web.accessLogs.target to console to write it to standard output only, or to both to write it to the file and to standard output. The default value, file, keeps writing it to the file only.
Also see Server logs.
CSRF token delivered as a response header
The CSRF token is now exposed in an X-XSRF-TOKEN response header and read from that header, instead of being placed in a cookie that page scripts can read. As a result, SonarQube Community Build works behind a reverse proxy that forces the HttpOnly attribute on all cookies.
Also see Web API.
Version 26.9.0.129388
Languages
Go
Go 1.27 is now supported. Improvements have been made to rule S3776 (Cognitive Complexity of functions should not be too high), which now accounts for the Go error-checking pattern.
For more information about this language analysis, see Go.
IaC (Infrastructure as Code)
False positives have been reduced in Terraform for resources declared with count or for_each, Cosmos DB accounts using continuous backup, and Cloud SQL instances configured with ssl_mode, and clear-text protocol detection has been refined for Kubernetes. Improvements have been made to the following rules:
S5332: Using clear-text protocols is security-sensitive (Kubernetes)
S6249: Authorizing HTTP communications with S3 buckets is security-sensitive (Terraform)
S6258: Disabling logging is security-sensitive (Terraform)
S6364: Defining a short backup retention duration is security-sensitive (Terraform)
S6403: Creating GCP SQL instances without requiring TLS is security-sensitive (Terraform)
For more information about these language analyses, see Azure Resource Manager, CloudFormation, Docker, Kubernetes/Helm, and Terraform.
Secrets
JSON Web Tokens and HTTP authentication credentials are now detected. Private keys that do not use standard PEM armor are also detected, and false positives have been reduced on example and test tokens, on identifiers, and on SOPS-encrypted values. The following rules are affected:
S6706: Cryptographic private keys should not be disclosed
S7403: Contentful Content Delivery API keys should not be disclosed
S8135: JSON Web Tokens should not be disclosed
S8136: HTTP authentication credentials should not be disclosed
A new sonar.secrets.demoMode analysis property turns off the filters that suppress placeholder, test, and low-entropy values, so secret detection can be demonstrated on sample code.
For more information about this language analysis, see Secrets.
Analysis
New lines of code (new_ncloc) metric
A New lines of code measure (new_ncloc) is now reported for the new code period. It applies the Lines of code definition to new code, counting physical lines that contain at least one character which is neither a whitespace nor a tabulation nor part of a comment.
New lines of code is the size measure on project cards in the new code view, in pull request and branch summaries, and in the Size domain of the Measures page, and it sizes and sorts new code treemaps. Values appear as projects are analyzed.
See the Size article on the Understanding measures and metrics page.
Issues in unchanged code no longer appear in new code
When SCM data is available, issues are now always backdated to the last change of the line they are raised on. As a result, issues on code that has not changed are no longer counted in the new code period.
User interface
Dark mode
Dark mode is now available. In your account menu, go to My account > Appearance and select Dark theme, Light theme, or Sync with system.
Also see Managing your account.
Issue sorting by priority
The issues page can now sort issues by Priority, so you can focus on the most impactful issues first. In MQR mode, Priority lists Security and Reliability issues first, from highest to lowest severity, followed by Maintainability issues. In Standard Experience, it lists vulnerabilities, then bugs, then code smells. It is the new default sort order, and you can also sort issues by file name or creation date.
For more information, see Retrieving issues.
Administration
Project history storage
SonarQube Community Build now stores project history to support future feature development. To control how long that history is kept, change the retention period at Administration > Configuration > General settings > Housekeeping. Set it to zero if you do not want to store history at all.
Also see Housekeeping.
Version 26.8.0.126808
Languages
The type of the security hotspot rules has been changed to vulnerability for several languages.
.NET / C#
Improvements have been made to the following rules, which now also raise on Entity Framework IQueryable query chains:
S1155: "empty()" should be used to test for emptiness
S2971: "IEnumerable" LINQs should be simplified
S3169: Multiple "OrderBy" calls should not be used
S3981: Collection sizes and array length comparisons should make sense
S6444: Regular expressions should be executed with a timeout
For more information about this language analysis, see C#.
HTML
Label association detection has been improved and false positives on accessibility rules have been reduced. Improvements have been made to the following rules:
S1082: Mouse events should have corresponding keyboard events
S6842: Non-interactive DOM elements should not have interactive ARIA roles
S6853: Label elements should have a text label and an associated control
For more information about this language analysis, see HTML.
IaC (Infrastructure as Code)
Improvements have been made to the following rules:
S2068: Hard-coded credentials are security-sensitive (Kubernetes)
S6329: Public network access to cloud resources should be disabled (Azure Resource Manager, CloudFormation, Terraform)
S6387: Azure role assignments should not be scoped to an entire subscription or management group (Azure Resource Manager, Terraform)
S6418: Secrets should not be hard-coded (Kubernetes)
S6471: Docker containers should not run as a privileged user (Docker)
For more information about these language analyses, see Azure Resource Manager, CloudFormation, Docker, Kubernetes/Helm, and Terraform.
Java
The following new rules for Jakarta EE, JPA, Quarkus, Spring, and Mockito have been added:
S5673: Spring components should use specialized annotations
S8908: Methods annotated with "@CacheResult" should not return void
S8909: "CacheKeyGenerator" implementations should be instantiable by the framework
S8910: Interfaces annotated with "@Mapper" should contain at least one "@DaoFactory" method
S8911: Methods annotated with "@Startup" should be non-static, non-producer, and parameter-free
S8912: Custom CredentialsProvider implementations should be annotated with @Unremovable
S8913: REST Data with Panache resource interfaces should not have implementation classes
S8947: JPA entity classes should not be final
S8948: "@OneToMany" relationships should use "mappedBy" or "@JoinColumn"
S8954: Bean Validation constraints should not be placed on static fields
S8975: The return value of "EntityManager.merge()" should be used
S8983: Stateless session beans should not store mutable state in instance variables
S9015: Mock should be created automatically with @Mock if @ExtendWith(MockitoExtension.class) is used
S9017: Mockito stubbing chains should be complete
S9021: "@Configuration" classes should not be final
S9024: @InjectMocks should be preferred over manual initialization
For more information about this language analysis, see Java.
JavaScript, TypeScript, CSS
New rules for testing frameworks have been added, covering Testing Library, Vitest, and browser-driven UI tests:
S2925: No fixed waits in tests
S5976: Similar tests should be grouped in a single Parameterized test
S8959: UI test debug commands should not be used
S8960: Test and hook callbacks should use a single completion style
S8967: Inline snapshots should not contain interpolations
S8968: Tests should be skipped explicitly
S8980: Disallow unnecessary act wrapping of Testing Library utilities
S8981: Disallow the global regexp flag in Testing Library queries
S8985: Side effects should not be performed in "waitFor" callbacks
S8990: Disallow passing a promise to fireEvent
S9011: button elements should have an explicit type attribute
S9012: Snapshots should not be generated inside Testing Library async utilities
S9020: Use "find*" to query Testing Library elements that may not be available yet
S9026: Promises returned by Testing Library async queries should be handled
S9027: Testing Library queries should match presence assertions
Vue support has been extended with the following new rules:
S8957: Vue component props should declare a type
S8982: HTML elements with v-for should have a :key attribute
S8984: Vue v-for directives should be valid
S8987: "v-if" and "v-for" should not be used on the same element
S8988: Side effects should not be performed inside Vue computed properties
S9019: Vue refs should not be used as operands
S9025: Asynchronous actions should not be used in Vue computed properties
False positives have been reduced on accessibility, assertion, and promise-handling rules, and duplicate attributes in Vue templates are now also reported. Improvements have been made to the following rules:
S1534: Member names should not be duplicated within a class or object literal
S1848: Objects should not be created to be dropped immediately without being used
S2486: Exceptions should not be ignored
S2699: Tests should include assertions
S2871: "Array.prototype.sort()" and "Array.prototype.toSorted()" should use a compare function
S3504: Variables should be declared with "let" or "const"
S6479: JSX list components should not use array indexes as key
S6551: Objects and classes converted or coerced to strings should define a "toString()" method
S6582: Optional chaining should be preferred
S6759: React props should be read-only
S6767: Unused React typed props should be removed
S6819: Prefer tag over ARIA role
S7766: Ternary expressions should be replaced with "Math.min()" or "Math.max()" for simple comparisons
S8780: Async test assertions should be awaited or returned
S8784: Assertions should be placed inside test cases or hooks
For more information about this language analysis, see JavaScript, TypeScript, CSS.
Python
New rules for Pydantic have been added, along with a set of rules targeting test files:
S3415: Assertion arguments should be passed in the correct order
S5778: Only one method invocation is expected when testing runtime exceptions
S5779: Assertions should not be made within the try block of a try-except catching AssertionErrors
S5863: Assertions should not be given twice the same argument
S5958: Tests should check which exception is thrown
S5976: Similar tests should be grouped in a single Parameterized test
S8714: Dedicated exception assertions should be used instead of "try-catch" with "fail()"
S8963: Pydantic models should not use multiple inheritance with conflicting configurations
S8966: pydantic-core serialization calls should provide fallback handlers
S8971: "SkipValidation" should not be combined with validation constraints
S8973: Double leading underscores should not be used for private attributes in Pydantic models
S8974: "json_schema_input_type" should not be used with "mode='after'" field validators
For more information about this language analysis, see Python.
Secrets
Detection of base64-encoded secrets has been improved, and JWT detection now covers base64url encoding. Improvements have been made to the following rules:
S6418: Secrets should not be hard-coded
S8215: Password hashes should not be disclosed
For more information about this language analysis, see Secrets.
XML
Improvements have been made to rule S2068 (Hard-coded credentials are security-sensitive), reducing false positives.
For more information about this language analysis, see XML.
API
Pull request ID returned by the pull requests list endpoint
The response of the api/project_pull_requests/list endpoint now includes a pullRequestId field.
For more information, see Web API.
Deployment
IPv6 support in the Docker image and Helm chart
The Docker image now listens on both IPv4 and IPv6 addresses automatically. In the Helm chart, probes are compatible with IPv6 and the network policy allows IPv6 (::/0) egress.
For more information, see Set up and start your container and Customizing Helm chart.
Version 26.7.0.124771
Improved default issue search
The default issue list no longer groups results by component. Issues are now sorted by severity first and by software quality second (Security, then Reliability, then Maintainability). In Standard Experience mode, issues are sorted by standard severity first and by type second (Vulnerability, Bug, Code Smell).
Security scanning limitations banner for SonarQube Community Build
A message on the project Overview page now informs you that SonarQube Community Build doesn't scan for critical injection vulnerabilities such as SQL injection and XSS, with a link to explore the commercial editions that provide this coverage.
Languages
The type of the security hotspot rules has been changed to vulnerability for several languages.
Go
Go 1.26.4 is now supported. In addition:
The
//nolintsuppression directive is now honored.Protobuf-generated files (
*.pb.go) are excluded from analysis by default.Analysis of directories that contain a large number of files is faster.
For more information about this language analysis, see Go.
HTML
The following improvements have been made:
Issue suppression is now supported through SonarQube's sonar-resolve workflow.
Twig comments are recognized.
The allowlist of ARIA roles for rule S6819 is now configurable.
New rules have been added:
S7039: Content Security Policies should be restrictive
S7071: Sandboxing should be enabled
S7074: webSecurity should be enabled
For more information about this language analysis, see HTML.
IaC (Infrastructure as Code)
New cloud security rules have been added:
S8793: RDS database instances should not be publicly accessible
S8847: Azure Key Vaults should enable purge protection
S8857: GCP Cloud Storage buckets should enforce uniform bucket-level access
Java
Java 26 analysis is now supported. New rules have been added:
S8714: Use assertThrows/assertDoesNotThrow instead of try-catch with fail()
S8715: JUnit 5 @Test's should not use JUnit 4 assertions
S8745: Test classes should not contain multiple @BeforeEach, @AfterEach, and similar annotations
For more information about this language analysis, see Java.
JavaScript, TypeScript, CSS
Issue suppression is now supported through SonarQube's sonar-resolve workflow. New rules for testing frameworks and assertions have also been added:
S1244: Floating point numbers should not be tested for equality
S5845: Assertions comparing incompatible types should not be made
S5906: The most specific assertion should be used
S8754: Test titles should be unique within the same suite
S8780: Async test assertions should be awaited or returned
S8781: Test and suite titles should not be empty or whitespace-only
S8782: Lifecycle hooks should be declared before test cases
S8783: Forced browser interactions should not bypass actionability checks
For more information about this language analysis, see JavaScript, TypeScript, CSS.
PHP
Detection for rule S4790 (weak hashing) has been improved, reducing false positives.
For more information about this language analysis, see PHP.
Secrets
The following improvements have been made:
The list of file extensions excluded from secret detection, previously hard-coded, is now customizable.
Test-file detection, performance, and logging have been improved.
The known-fake-secret filter discards secret candidates that match a rule's list of fake or placeholder values (repeated characters, placeholder tokens, documentation examples). The new sonar.secrets.disableKnownFakeSecretFilter property (default false) turns this filter off when set to true, reporting those candidates as low-confidence matches, which is useful when evaluating secret detection on a benchmark project.
For more information about this language analysis, see Secrets.
API
Consistent logging on API v2 endpoints
Logging behavior for exceptions thrown by API v2 endpoints is now consistent with API v1, using the appropriate log levels for each type of exception.
Version 26.6.0.123539
Languages
The type of the security hotspot rules has been changed to vulnerability for several languages.
Azure Resource Manager
New rules have been added:
S8679: Personal or corporate user accounts should not be used for API connections
S8680: Basic authentication should not be used for Azure Logic Apps API connections
S8681: Azure Logic Apps hard-coded secrets are security-sensitive
S8682: Azure Logic Apps actions should enable Secure Inputs and Secure Outputs
S8683: Azure Logic Apps should use structured error handling
S8684: Azure Logic Apps control actions should not be excessively nested
HTML
A new rule has been added:
S8687: Enforce the HTML "lang" attribute against a configured list of ISO 639-1 language codes
API
Allow searching case insensitive in api/projects/search
The parameter projectKeys has been added to the /api/projects/search endpoint to allow users to do case-insensitive search of project keys.
Analysis
Support overlapping start and end locations in issue import format
The previous release version requests that the end position is strictly after the start position in the external issue format. SonarQube Community Build can now process issues from external reports when startColumn equals to the endColumn.
Version 26.5.0.122743
Languages
Go
Test files are now only analyzed by rules applicable to test files, reducing noise and improving precision.
Rust
The Rust analyzer now supports the following Clippy rules when importing a Clippy report:
disallowed_fieldsduration_suboptimal_unitsmanual_checked_opsmanual_takeunnecessary_trailing_comma
.NET / C#
Support for the Cobertura coverage file format was added. Cobertura report paths can be passed via the sonar.cs.cobertura.reportsPaths parameter.
IaC (Infrastructure as Code)
The IaC analyzer was updated with false-positive reductions across analyzers.
Version 26.4.0.121862
Analysis performance
Better handling of large JaCoCo reports
SonarQube now better supports large aggregate JaCoCo coverage reports, improving stability and scalability for large monorepos and multi‑module builds with consolidated coverage.
Languages
IaC
The infrastructure‑as‑code analyzer was updated to reduce false positives for existing rules, add support for multi‑document Helm charts, and improve Bicep parsing.
Java
Support for Java 25 is extended with additional rules in the Java analyzer:
S8446 – Only one main method should be present
S8465 – ScopedValue instances should be assigned to a stable reference
S8469 – Use IO.readln(String prompt) instead of IO.print + IO.readln()
S8447 – Initialize subclass fields before super() when superclass constructor may call overridable methods
S8450 – Use IO.readln() instead of BufferedReader boilerplate for console input
S3051 – Main methods should be used only as program entry point
PHP
PHP analysis has been improved based on user feedback to reduce noise from “PITA” rules and improve precision.
Text
The text analyzer was updated to bring a new rule to detect Glassworm‑style attacks and additional hardening improvements.
S8703 – Unicode Variation Selectors should not hide executable content
Deployment
Elasticsearch metrics
New Elasticsearch metrics have been introduced to detect disk‑space related issues earlier and provide better observability.
Version 26.3.0.120487
New navigation and workspace experience
A modernized navigation and workspace experience is now available in SonarQube Community Build.
The key changes are:
Vertical Navigation: We’ve moved the horizontal top menu to a vertical sidebar. This makes navigating between different spaces faster and more intuitive.
Updated information architecture: Navigation items are now grouped to be easier to find contextually (e.g., Analysis, Reporting, Policies, Project).
New context switcher: A new area in the left navigation bar allows you to easily jump between projects without losing your place.
Improved failed SARIF import logs
More details are now logged on SARIF reports import errors.
Improved API performance
The performance of the api/permissions/search_templates Web API for large data sets has been improved.
Languages
Go
It’s now possible to disable the Go analyzer in the UI or via the sonar.go.activate property.
New Go analysis engine delivering up to a 30x speedup in processing.
Java
The following rules have been added to support Java 25:
S8432 : "ScopedValue.where" results should not be ignored
S8433: should not raise issue for classes without superclass declared
S8444 - Validation and data preparation logic before super() should not bloat constructor
S8445: Group import declarations by specificity
Python
New rules for FastAPI and Flask framework.
S8370: Query parameters should not be used in Flask POST requests
S8371: HTTP headers should be accessed safely to avoid KeyError exceptions
S8374: Flask class-based view decorators should be applied using the "decorators" attribute
S8375: Flask "preprocess_request()" return values should be handled
S8389: FastAPI file upload endpoints should use "Form()" with Pydantic validators instead of "Body()" or "Depends()"
S8392: FastAPI applications should not bind to all network interfaces
S8396: Optional Pydantic fields should have explicit default values
S8397: FastAPI applications should be passed as import strings when using reload, debug, or workers
S8400: Endpoints returning 204 status should have an empty response body
S8401: Child routers should be included before parent router registration
S8405: TestClient requests should use "content" parameter for bytes or text
S8409: FastAPI routes should not specify redundant "response_model" parameters
S8410: FastAPI dependencies should use "Annotated" type hints
S8411: FastAPI path parameters should be included in route function signatures
S8412: Generic route decorators should not be used
S8413: Router prefixes should be defined during "APIRouter" initialization
S8414: CORSMiddleware should be added last in the middleware chain
S8415: HTTPException responses should be documented in endpoint metadata
Ruby
The following rules have been added (in Beta):
S8418: Unused method and block parameters should be removed or prefixed with an underscore
S8419: Function parameters should not be immediately reassigned
S8421: Underscore-prefixed variables should not be used
S8422: Trailing underscores in multiple assignment should be removed
S8423: Parameter default values should not reference themselves
S8424: Constants should not be reassigned
S8425: Constants should be explicitly scoped to avoid ambiguous resolution
S8426: Variables should not be assigned only to be implicitly returned
The following rules were removed because they raised too many false-positives:
S1854: Unused assignments should be removed
S7819: Variables and methods should be accessible in their usage context
New GitLab PAT format added for secret detection
The rule S6690: GitLab tokens should not be disclosed has been improved to add the new GitLab PAT format.
Version 26.2.0.119303
Languages
.NET 10 and C# 14 support
Empowers .NET teams to adopt the Long Term Support (LTS) release of .NET 10 and C# 14 immediately, ensuring their analysis remains accurate, performant, and free of false positives associated with new language constructs.
Related rules:
S1121: Assignments should not be made from within sub-expressions
S1144: Unused private types or members should be removed
S2225: "ToString()" method should not return null
S2292: Trivial properties should be auto-implemented
S2325: Methods and properties that don't access instance data should be static
S2583: Conditionally executed code should be reachable
S2589: Boolean expressions should not be gratuitous
S2692: "IndexOf" checks should not be for positive numbers
S2953: Methods named "Dispose" should implement "IDisposable.Dispose"
S2970: Assertions should be complete
S3063: "StringBuilder" data should be used
S3264: Events should be invoked
S3398: "private" methods called only by inner classes should be moved to those classes
S3459: Unassigned members should be removed
S3877: Exceptions should not be thrown from unexpected methods
S3928: Parameter names used into ArgumentException constructors should match an existing one
S4545: "DebuggerDisplayAttribute" strings should reference existing members
S7039: Content Security Policies should be restrictive
PHP
Reduces false positives on several rules and cleans up build and dependency infrastructure. Related rules:
S1155: "empty()" should be used to test for emptiness
S1172: Unused function parameters should be removed
S2699: Tests should include assertions
S1068: Unused "private" fields should be removed
Scala
Includes fixes to false positives and negatives for the following rules:
S1192: String literals should not be duplicated
S126: "if ... else if" constructs should end with "else" clauses
VB6
Fixes parse errors and line count. Related rules:
S138: Subs and functions should not have too many lines
S1151: "Case" clauses should not have too many lines
Version 26.1.0.118079
Quality gate fudge factor improved
The quality gate fudge factor refers to a mechanism where conditions on duplication and coverage are ignored. This is used to avoid overly strict enforcement when dealing with small changes, as minor issues might disproportionately impact the overall quality gate status.
In the previous version, these conditions were ignored until the number of new lines was at least 20. With this new version:
The conditions on duplication are ignored until the number of new lines is at least 20 (no change).
The conditions on coverage are ignored until the number of new lines to cover is at least 20.
Direct navigation from project to bound repo
The bound to repo icon displayed in the header of a SonarQube Community Build project is now clickable and opens the respective repository in the DevOps platform.
Version 25.12.0.117093
Login page improvement
The SonarQube Community Build login page has been changed to improve your user experience.
CSS rules for accessibility
The following CSS accessibility rules have been added:
S7923: Orientation of the page is not restricted using CSS transform property
S7924: Text has minimum contrast
S7925: Spacing and height in style attributes is not `!important`
Quick fixes for JavaScript / TypeScript
Additional 58 rules for JavaScript / TypeScript can now provide quick fixes in SonarQube for IDE.
Python 3.14 rules
The following rules have been added to support Python 3.14:
S7932: Return, break, or continue statements should not exit finally blocks
S7940: Unnecessary parentheses should not surround single exception types
S7941: Compression modules should be imported from the compression namespace
S7942: Template strings should be processed before use
S7943: Template and str should not be concatenated directly
S7944: Template strings should not be used for simple string formatting
S7945: Template string processing should use structural pattern matching
Version 25.11.0.114957
In-product communication of product news
Sonar will now provide in-product notifications to users regarding important product updates. These messages will be tailored to specific audiences. Users will receive alerts for new messages and will have access to a complete message history.
PHP 8.5 support
PHP version 8.5 is now supported.
Python 3.14 support
Python version 3.14 is now supported.
High-volume file move detection
SonarQube now stops the analysis when a high-volume file move is detected and raises a warning to let users revert to their initial project configuration in case of an unintended file move.
DevOps platform integration
GitHub Enterprise Cloud with Data Residency now supported
SonarQube’s integration with GitHub Enterprise Cloud with Data Residency is now supported.
Navigation from SonarQube to GitHub
You can now navigate from your SonarQube project to the bound GitHub repository by selecting the project bound icon.
Version 25.10.0.114319
Go 1.25 support
Go version 1.25 is now supported.
JavaScript analysis improved
68 rules from the eslint-plugin-unicorn have been added to the JavaScript analysis.
Parallel execution of Python rules
Parallel execution of Python rules is now supported. See Parallel code scan for more information.
JRE auto-provisioning can be disabled at the instance level
JRE auto-provisioning for the scanners on CI/CD host is enabled by default. It was possible to disable it through an analysis parameter. You can now disable it at the SonarQube instance level. See Managing JRE auto-provisioning for more information.
Version 25.9.0.112764
AWS lambda rules for Python
The following rules related to AWS lambdas and common practices have been added to the Python analysis:
S6249: Authorizing HTTP communications with S3 buckets is security-sensitive
S7613: AWS Lambda handlers should return only JSON serializable values
S7609: AWS CloudWatch metrics namespace should not begin with `AWS/`
S6246: Lambdas should not invoke other lambdas synchronously
S7608: S3 operations should verify bucket ownership using ExpectedBucketOwner parameter
S7618: Network calls in AWS Lambda functions shouldn't be made without explicit timeout parameters
S7617: Reserved environment variable names should not be overridden in Lambda functions
S6243: Reusable resources should be initialized at construction time of Lambda functions
S6262: AWS region should not be set with a hardcoded String
S7622: boto3 operations that support pagination should be performed using paginators or manual pagination handling
S7621: AWS waiters should be used instead of custom polling loops
S7620: AWS Lambda handlers should clean up temporary files in /tmp directory
S7625: Long-term AWS access keys should not be used directly in code
S7614: AWS Lambda handlers must not be an async function
S7619: "botocore.exceptions.ClientError" must be explicitly catch and handled
AngularJS rules for TypeScript
The following rules related to AngularJS have been added to the TypeScript analysis:
S7655: Angular classes should implement lifecycle interfaces for their lifecycle methods
S7641: Angular lifecycle methods should be used in the correct context
S7656: Angular Pipes should implement PipeTransform interface
S7650: Components and directives should not use the "inputs" metadata property
S7648: Components, Directives, and Pipes should use standalone architecture
S7647: Empty Angular lifecycle methods should be removed
S7649: Input bindings should not be aliased
S7653: Output bindings should not be aliased
S7652: Output bindings should not be named "on" or prefixed with "on"
S7651: Output bindings should not be named as standard DOM events
S7654: The "outputs" metadata property should not be used in Angular components and directives
PHP analysis improved
PHP keyword parsing has been optimized by replacing the regex-based logic.
Secret detection improved
Performance improved.
Rust analysis improved
The Clippy analysis can now be run offline by setting sonar.rust.clippy.offline to true. This prevents Clippy from trying to fetch dependencies. Dependencies must still be available locally for the analysis to work correctly. This setting is intended for air-gapped environments.
Version 25.8.0.111929
Improved issue suppression for Python
Individual rules can be suppressed in Python using the rule key with # NOSONAR (eg #NOSONAR(S5655)). Additionally, the rules below can be enabled to track usage of # NOSONAR and # noqa:
S1291: Track uses of "NOSONAR" comments
S1309: Track uses of noqa comments
You can detect correct usage of # NOSONAR & # noqa with rule:
S7632: Issue suppression comment should have the correct format
New rules for Java 24
Ensures that the Java analyzer successfully parses Java 24 source files without errors and correctly handles new Java 24 features. Adds Java 24-specific rules and updates existing rules to ensure they properly use new language constructs in Java 24.
Relevant rules:
S6906: Virtual threads should not run tasks that include synchronized code
S2093: Try-with-resources should be used
S7478: "transformClass" method should be used instead of "build" when transforming a class
S7477: Class name should be omitted when unchanged by class transform
S7479: "ClassBuilder.withMethodBody" should be preferred to "ClassBuilder.withMethod"
S7482: Don't provide an initializer for a stateless stream gatherer
S7629: When a defaultFinisher is passed to a Gatherer factory, use the overload that does not take a finisher
S7481: Gatherer.ofSequential() should be used to build sequential gathers
Kontlin 2.2 support
SonarQube analysis now supports Kotlin 2.2.
Version 25.7.0.110598
Improved Go analysis precision
The precision of the GO analysis has been improved thanks to a cross-file type resolution.
Java analyzer better identifies performance issues
The following rules have been added to better identify performance issues.
S4030 - Collection and array contents should be used
S3063 - "StringBuilder" data should be used
S3024 - Arguments to "append" should not be concatenated
S3033 - ".length" should be used to test for the emptiness of StringBuffers
The following rule has been improved:
S7158 - "String.isEmpty()" should be used to test for emptiness The rule has been extended to work with all CharSequence.
Support for Java 24
SonarQube can now analyze a Java 24 project.
Other Java improvements
The following rules have been added for Java 23:
S7474 - Markdown, HTML and Javadoc tags should be consistent
S7476 - Comments should start with the appropriate number of slashes
The following rules have been improved:
False positive correction: S125, S1123, S1854, S2384
False negative correction: S1943
Improved Python analysis on comprehensions and coroutines
The following new rules have been added on comprehensions and coroutines:
S7483: Asynchronous functions should not accept timeout parameters
S7484: Events should be used instead of sleep in asynchronous loops
S7491: Checkpoints should be used instead of sleep(0)
S7494: Unnecessary generator - rewrite as a comprehension
S7486: Long sleep durations should use sleep_forever() instead of arbitrary intervals
S7488: Use non-blocking sleep functions in asynchronous code
S7499: Async functions should not contain synchronous http operations
S7492: Unnecessary list comprehension in <any/all>() prevents short-circuiting - rewrite as a generator
S7500: Unnecessary <dict/list/set> comprehension - rewrite using <dict/list/set>()
S7496: Unnecessary <list/tuple> passed to tuple() - rewrite as literal or remove call
S7503: Async functions should use async features
S7498: Unnecessary empty <dict/list/tuple> call - rewrite as a literal
S7501: Async functions should not contain input() calls
S7497: Cancellation exceptions should be re-raised after cleanup
S7504: Unnecessary `list()` cast on iterable
S7505: Unnecessary map usage - rewrite using a generator expression/<list/set/dict> comprehension
S7506: Dictionary comprehensions shouldn't use a static key
S7507: Incorrect `default_factory` keyword argument for `defaultdict`
S7493: Async functions should not contain synchronous file operations
S7490: Cancellation scopes should contain checkpoints
S7510: Unnecessary <reversed> call around sorted()
S7489: Async functions should not contain synchronous OS calls
S7502: Asyncio tasks should be saved to prevent premature garbage collection
S7487: Async functions should not contain synchronous subprocess calls
S7508: Unnecessary <list/reversed/set/sorted/tuple> call within <list/set/sorted/tuple>()
S7511: Unnecessary subscript reversal of iterable within <reversed/set/sorted>()
S7512: Inefficient dictionary iteration method
S7516: Unnecessary sort inside set
S7517: Use dict.items() to iterate over a dictionary
S7513: TaskGroup/Nursery should not be used for a single start call
S7519: Unnecessary dict comprehension - rewrite using dict.fromkeys()
S7515: async with should be used for asynchronous resource management
S7514: Control flow statements should not be used inside TaskGroup or Nursery blocks
Python option added to analysis build tool
A Python tab is now available in SonarQube’s project analysis build tool.
Improved .NET analysis
The following rules have been improved:
False positive correction: S2068, S3626
False negative correction: S1168, S3878, S1871, S2068
Helm chart now with hostpath storage
It’s now possible to save data with hostpath in SonarQube Helm charts.
Version 25.6.0.109173
SonarQube detects secret leaks within hidden files
SonarQube can detect secret leaks in files located within directories or hidden files that begin with a dot.
Default Quality Gate
As a Quality Gate administrator you can now set a default Quality Gates that is not compliant with Clean as You Code. See Changing default quality gate for more details.
Version 25.5.0.107428
New language: Rust
Rust analysis is now supported.
It offers:
85 rules
Code Coverage import (LCOV and Cobertura formats)
Cognitive Complexity metric
Cyclomatic Complexity metric
Import of Clippy output as external rules (JSON format)
See Rust for more information.
Java analysis improved
In addition to the mobile security improvement, the Java analyzer has been improved as follows:
Java 23 analysis is now supported.
The following rules targeting Java 22 code have been added:
S7467 - Unused exception parameter should use the unnamed variable pattern
S7466 - Use `var` instead of a type with unnamed variable _
S7475 - The type of an unused component should be removed from pattern matching
Kubernetes analysis improved
The Kubernetes analysis has been improved:
It’s now possible to disable the analysis of Helm files.
The
sonar.kubernetes.file.suffixesproperty is now handled correctly.
.NET analysis improved
The following rules have been improved:
S2222 - Locks should be released on all paths: The locking via lock object primitives is now supported.
S4158 - Empty collections should not be accessed or iterated: LinkedList is now supported.
Version 25.4.0.105899
Kotlin analysis
Over 80 rules have been rebuilt to support Kotlin 2.0 and the new K2 compiler. As a result, Kotlin analysis is now 50% faster than before this release. Kotlin developers can now not only use Sonar to analyze Kotlin 2.0 and newer, but it also performs better than before.
Version 25.3.0.104237
Java rules
The following Spring Java rules have been added:
S7177: Use appropriate @DirtiesContext modes
S7178: Injecting data into static fields is not supported by Spring
S7179: @Cacheable and @CachePut should not be combined
S7180: "@Cache*" annotations should only be applied on concrete classes
S7183: @InitBinder methods should have void return type
S7184: "@Scheduled" annotation should only be applied to no-arg methods
S7185: @eventlistener methods should have one parameter at most
S7186: Methods returning "Page" or "Slice" must take "Pageable" as an input parameter
S7190: Methods annotated with "@BeforeTransaction" or "@AfterTransaction" must respect the contract
The following Spring Java rules have been improved:
S6856: "@PathVariable" annotation should be present if a path variable is used This rule will now raise an issue if a method has a path template with a placeholder, but no corresponding
@PathVariable, or vice-versa.S6809: Methods with Spring proxy should not be called via "this" This rule will now also check for methods annotated with Spring’s
@Cacheableannotation.
Go 1.23 now supported
SonarQube Community Build now supports the analysis of Go 1.23 code.
PHP analysis
The elseif keyword is now taken into account during the Cyclomatic Complexity calculation. See the Complexity article on the Understanding measures and metrics page.
IPv6 support
SonarQube Community Build (the ZIP or Docker installation) now supports IPv6 addresses. An additional configuration is required. For setup information, see Enabling IPv6 in Zip installation and Enabling IPv6 in Docker installation.
Version 25.2.0.102705
Java 21 is now supported
SonarQube Community Build can now run in a Java 21 environment.
Version 25.1.0.102122
Faster analysis bootstrap
To improve analysis efficiency, we’ve shortened the time it takes to load the active rules in your quality profile.
Improvement to BitBucket server onboarding
To improve the import of BitBucket repositories, you can now browse and easily import all the projects from the onboarding page, without any limitation of number.
Language updates
PHP analysis now supports asymmetric property visibility (PHP 8.4).
Version 24.12.0.100206
Introducing Multi-Quality Rule Mode
You can now toggle your SonarQube Community Build instance between the Standard Experience and MQR mode.
See instance mode Overview for more information. In both modes, it’s possible to customize the severity of issues and rules.
New SonarQube Server instances use MQR Mode by default. Upon upgrading, existing SonarQube Server 10.1 and earlier are configured with the Standard Experience by default.
Python
Python 3.13 is now supported.
Java
Analysis of Java 22 Projects is now supported.
JSpecify annotations are now supported with one new rule.
24 main code rules enabled for test code.
.NET / C#
Analysis of C#13 is now supported, and the rules have been updated to support .NET 9. We also added 3 new advanced rules around locking and misuse Linq queries on collections known to not be empty.
Kotlin
Analysis of Kotlin 2.0 is now supported.
Update notes
This section contains notes about breaking changes and important updates to be aware of before updating to a new version.
Latest release - 26.11.0.134175
Ruby, Rust, and Scala analyzers are no longer included
SonarQube Community Build no longer includes the Ruby, Rust, and Scala analyzers. When you update, their rules are removed from all quality profiles, and their issues are closed on the next analysis of each project. Closed issues are shown as fixed. Analysis of these languages remains available in all commercial editions of SonarQube Server and in all SonarQube Cloud plans, including the Free plan. You can also install the community-maintained plugins manually from sonar-ruby, sonar-rust, and sonar-scala. If you install a plugin within 30 days of the analysis that closed the issues, the issues are reopened with their previous status, such as Accepted or False positive. You need to reactivate the rules in your custom quality profiles.
For more information, see the community announcement.
Advanced reliability rules for Java and Python are no longer included
SonarQube Community Build no longer includes the advanced reliability rules for Java and Python. When you update, these rules are removed from all quality profiles, and their issues are closed on the next analysis of each project. Closed issues are shown as fixed. The rules remain available in all commercial editions of SonarQube Server and in all SonarQube Cloud plans, including the Free plan. You can also install the community-maintained plugins manually from the SonarQubeCommunity organization on GitHub. If you install a plugin within 30 days of the analysis that closed the issues, the issues are reopened with their previous status, such as Accepted or False positive. You need to reactivate the rules in your custom quality profiles.
For more information, see the community announcement.
Migration of existing Security Hotspots to issues
Run the migration only on SonarQube Community Build 26.11 or later. In SonarQube Community Build 26.9 and 26.10, a known issue can cause migrated hotspots that you reviewed as Safe or Fixed to reappear as new Open issues after the next analysis. If you already ran the migration on one of these versions, see Repairing a migration run on 26.9 or 26.10.
Security Hotspots are being phased out. Rules that previously raised hotspots now raise vulnerabilities or code smells (in Standard Experience), which appear as security issues or maintainability issues (in MQR Mode). A system administrator can migrate existing hotspots to their new issue type through the api/hotspots/migrate_to_issues endpoint. Support for Security Hotspots will be removed in a future release, at which point the migration runs automatically during the update.
For more information, see Migrating security hotspots to vulnerabilities.
Docker image no longer trusts emSign ECC Root CA - G3
The SonarQube Community Build Docker image no longer trusts emSign ECC Root CA - G3, one of the eMudhra certificate authorities whose keys were compromised. This applies to Docker and Kubernetes installations. Scanners that use JRE auto-provisioning now get a Java runtime that no longer trusts the compromised certificate authorities. ZIP installations run on the Java runtime installed on your machine, so they still need the workaround.
For more information, see eMudhra certificate authority compromise.
Free disk space checked at startup
At startup, SonarQube Community Build now checks the free disk space of the Elasticsearch data directory. If the free space is below 10% of the disk size, or below 150 GB on disks larger than 1.5 TB, startup stops with a message that shows the available and required space. Make sure enough disk space is free before you update.
The DevOps platform integration page asks for your credential when you bind a project
When you bind a project to a DevOps platform repository, SonarQube Community Build uses a credential stored for your user account. It does not use the credentials set on the global DevOps platform integration. If you have no valid credential stored and you have the Create Projects permission, the DevOps platform integration page now asks for it. Without the Create Projects permission, the page does not show Save. For GitHub, authorize the GitHub App from Projects > Create Project > From GitHub before you bind the project.
For more information, see Binding an unbound project.
Previous releases
Version 26.10.0.133078
The Anyone group has been removed
The Anyone group, deprecated since SonarQube 9.8, has been removed from SonarQube Community Build. You can no longer grant permissions to it or revoke them from it, in the UI or through the web API. The group no longer appears in group and permission lists, and the api/permissions/add_group, api/permissions/remove_group, api/permissions/add_group_to_template, and api/permissions/remove_group_from_template endpoints return a 404 error when groupName is Anyone, in any letter case.
When you update, every permission the Anyone group held globally or on a project is migrated to the sonar-users group, so authenticated users keep the permissions they had through Anyone. Permissions granted to the Anyone group in permission templates are removed and not migrated. After updating, review your permission templates and grant the permissions you need to sonar-users or another group.
Unauthenticated users lose any permission they had only through Anyone, including Execute Analysis. If you rely on unauthenticated analysis, this is a breaking change. Public project visibility is not affected: it's a separate mechanism that still grants Browse and See Source Code to every user, including unauthenticated users when forced authentication is disabled.
For more information, see Managing groups and Disabling forced user authentication.
Sonar way core is the default only on new installations
Sonar way core becomes the default quality profile only on new installations. When you update to 26.10, your projects keep the quality profiles they used before, and the default profile of each language stays the same. To reduce the number of issues raised on a project, assign Sonar way core or Sonar way extended to it, or make one of them the default profile for a language.
Also see Built-in quality profiles and Changing default quality profile.
Access token required to bind a project to a DevOps platform
Binding a project to a GitLab, Azure DevOps, Bitbucket Cloud, or Bitbucket Data Center repository now requires the user who performs the binding to have their own access token stored in SonarQube Community Build. The credentials set on the global DevOps platform integration are no longer sufficient for this operation. This makes sure that users can only bind projects to repositories they have access to on the DevOps platform.
If no token is stored for your user account, saving the binding from Administration > Project coverage > Bind project fails with the message Personal access token for '<configuration name>' is missing. The Check configuration test in the global DevOps platform integration settings validates only the global credentials, so it succeeds even when your user account has no token stored.
To store a token for your user account, do one of the following:
Import a repository through Create project and select your DevOps platform. Before it lists your repositories, the import flow prompts you for a token: an API token for Bitbucket Cloud, or a personal access token for GitLab, Azure DevOps, and Bitbucket Data Center.
Call the
POST api/alm_integrations/set_patweb API endpoint while signed in as the user who will save the binding. That user account needs the Create Projects permission. Set thealmSettingparameter to the name of the DevOps platform configuration and thepatparameter to a valid token. For Bitbucket Cloud, also set theusernameparameter to the email address of your Bitbucket account.
After the token is stored, you can save the project binding.
Also see Binding an unbound project, Importing your GitLab repositories, Creating and configuring your Azure DevOps project, Importing Bitbucket Cloud repositories, and Importing your Bitbucket Data Center repositories.
Webhook validation blocks internal network destinations
When the Enable local webhooks validation setting (sonar.validateWebhooks) is enabled, which is the default, SonarQube Community Build now also rejects webhook URLs that resolve to link-local, site-local (private network), multicast, and cloud metadata addresses. Previously, the setting blocked only loopback and wildcard addresses and the addresses of the SonarQube Community Build host. The validation applies when you create or update a webhook and each time a webhook is delivered, including to redirect targets. As a result, existing webhooks that send payloads to a receiver on your internal network, such as a CI server at a 10.x.x.x or 192.168.x.x address, can stop working after you update.
If your webhooks must reach internal destinations, go to Administration > Configuration > General settings > Security and disable Enable local webhooks validation. Disabling the setting turns off address validation for all webhooks on the instance, including webhooks that project administrators create.
Also see Configuring webhooks.
Higher default heap size for the web and Compute Engine processes
The default maximum heap size has been raised from 512m to 1G for the web server process and from 512m to 1536m for the Compute Engine process. Instances that run close to their memory limit, and containers with a fixed memory allocation, need more memory than before. To keep your previous values, set sonar.web.javaOpts and sonar.ce.javaOpts explicitly. Setting one of these properties replaces its default value instead of extending it, so include every JVM flag you want to keep, or use sonar.web.javaAdditionalOpts and sonar.ce.javaAdditionalOpts to add flags without replacing the defaults.
Also see SonarQube instance.
Warning for non-system properties in sonar.properties
At startup, SonarQube Community Build now writes a warning to the server log for each property in sonar.properties that is not a recognized system property. A property set in this file cannot be managed from the UI or the web API, and it may have no effect. If the log shows this warning, set the property through the UI or the web API instead.
Also see Configuration methods.
Version 26.9.0.129388
None in this release.
Version 26.8.0.126808
PostgreSQL support for versions 15-18
Support for PostgreSQL versions is now from 15 to 18. Support for version 14 has been removed.
SonarQube Community Build includes Elasticsearch 9.x
SonarQube Community Build 26.8 and later includes Elasticsearch 9 (9.4.3). For more information, see Elasticsearch filesystem requirements.
Upgrading to Elasticsearch 9 triggers a full re-index. Because Lucene 10 cannot read the previous on-disk format, the index is rebuilt from scratch into a fresh es9 subdirectory. Your configured index location is preserved, but its contents are regenerated.
Version 26.7.0.124771
None in this release.
Version 26.6.0.123539
None in this release.
Version 26.5.0.122743
None in this release.
Version 26.4.0.121862
None in this release.
Version 26.3.0.120487
None in this release.
Version 26.2.0.119303
Java 25 support
SonarQube Community Build can now run on Java 25.
PostgreSQL 18 support
Support for PostgreSQL versions is now from 14 to 18, enabling deployments using the most recent PostgreSQL release. Support for version 13 has been removed.
Kubernetes 1.35 support
Support for Kubernetes versions is now from 1.32 to 1.35. Support for 1.30 and 1.31 has been removed.
Removed support for 2016 MSSQL Server 13.0
Supported MSSQL server is now 2022 (MSSQL Server 16.0); 2019 (MSSQL Server 15.0); 2017 (MSSQL Server 14.0). Support for 2016 MSSQL Server 13.0 support has been removed. See Installing database for more information.
Use of Elasticsearch 8.x
SonarQube Community Build now includes Elasticsearch 8.x, which requires write access to the /tmp directory. This is a requirement from Elasticsearch itself and cannot be disabled. For more information and a solution, see Elasticsearch 8.x filesystem requirements.
Version 26.1.0.118079
JDK now required
The SonarQube Community Build runtime now requires Java Development Kit (JDK). Note that the previous requirement of a Java Runtime Environment (JRE) is no longer sufficient; a full JDK is required. See Software requirements for details.
Downgraded Microsoft SQL JDBC Auth from 13.2.1 to 12.10.2
Due to changes in the Microsoft SQL JDBC driver, it was downgraded from version 13.2.1 to 12.10.2. See Using integrated security for details.
Version 25.12.0.117093
None in this release.
Version 25.11.0.114957
To use integrated security in Microsoft SQL database, upgrade to Microsoft SQL JDBC Auth 13.2.1 package. See Using integrated security for details.
Version 25.10.0.114319
None in this release.
Version 25.9.0.112764
None in this release.
Version 25.8.0.111929
None in this release.
Version 25.7.0.110598
None in this release.
Version 25.6.0.109173
None in this release.
Version 25.5.0.107428
None in this release.
Version 25.4.0.105899
None in this release.
Version 25.3.0.104237
Oracle database
Before running the migration, you must add an Oracle permission that will be needed only during the migration. To do so, use the command below.
For security reasons, we recommend to limit the permission to the SonarQube database user.
You can revoke the permission after the update.
Version 25.2.0.102705
None in this release
Version 25.1.0.102122
Update in PostgreSQL support
PostgreSQL versions 11 and 12 are no longer supported. Supported versions are now from 13 to 17.
SAML configuration update required
When configuring SAML on your SonarQube Server instance with assertion encryption, response signature must be enforced. You might need to update your SAML configuration:
If you use SAML with Microsoft Entra, make sure you sign the response by selecting Sign SAML response or Sign SAML response and assertion as the sign-in response. See Step 2 > If you use encryption, enforce response signature in Setup of security features.
If you use SAML with PingID, make sure you sign the response by selecting Sign Response or Sign Assertion & Response as the sign-in response. See Step 2 > To enable the encryption of SAML assertions in Setup of security features.
In addition, the assertion decryption now requires that you store also the public key certificate in SonarQube Community Build (not only the private key). Make sure the certificate is stored in SonarQube as follows:
In SonarQube Community Build, go to Administration > Configuration > General Settings > Authentication > SAML.
In SAML Configuration > SAML, select Edit. The Edit SAML configuration dialog opens.
In Service provider certificate, enter the certificate.
Server base URL setup now mandatory for SAML authentication
Your SAML authentication setup will not work if the SonarQube Server base URL is not set in SonarQube Server. See Server base URL.
Version 24.12.0.100206
None in this release.
Deprecations and removals
This section contains information on the deprecation and removal of SonarQube Community Build features and API endpoints. See the Deprecation policy for more information.
Latest release - 26.11.0.134175
Parameter pullRequest removed from api/project_analyses/search
The pullRequest parameter, which was never supported, has been removed from api/project_analyses/search. Remove it from any requests that use it.
Previous releases
Version 26.10.0.133078
ZIP installation will be removed in a future release
We recommend installing SonarQube Community Build with the Docker image or the Helm chart. ZIP installation is still available, but it will be removed in a future release. For more information, see From ZIP file. To move an existing ZIP installation, see the ZIP installation migration guide.
Deprecated custom rules APIs removed from the JavaScript analyzer
The Check, EslintBasedCheck, JavaScriptCheck, and TestFileCheck custom rules APIs of the JavaScript and TypeScript analyzer, deprecated for removal, have been removed. A custom rules plugin whose classes reference one of these types can fail to load. Update each custom rule class to implement EslintHook directly, and keep declaring it in CustomRuleRepository.checkClasses().
Parameter projectKey removed from api/hotspots/search
The projectKey parameter of api/hotspots/search, deprecated in favor of project, has been removed. Use the project parameter instead.
Version 26.9.0.129388
None in this release.
Version 26.8.0.126808
Java 17 support for SonarScanners has been removed
Support for Java 17 in SonarScanners has been removed in SonarQube Community Build version 26.8. Starting with version 26.8, Java 21 is required. If you use JRE auto-provisioning (enabled by default on supported scanners), no action is required as Java requirements are managed automatically. However, if auto-provisioning is disabled or unsupported, you must upgrade to Java 21 or newer. For more information, see General requirements.
Bitbucket Server deprecated
Following the end of Atlassian's support for Bitbucket Server, the integration with Bitbucket Server is deprecated. Use Bitbucket Data Center or Bitbucket Cloud instead.
Databases
PostgreSQL version 14 is not supported anymore.
Version 26.7.0.124771
Security Hotspots deprecation
Security Hotspots are being deprecated. Deprecation notices and badges now appear on the Security Hotspots pages, on the Security Review section of the Measures page, and on the Security Review Rating and Security Hotspot Count on the project summary page, each linking to the migration documentation. In the Web API, the /api/hotspots/* endpoints are marked as deprecated with information about their removal and the migration path.
Version 26.6.0.123539
None in this release.
Version 26.5.0.122743
None in this release.
Version 26.4.0.121862
None in this release.
Version 26.3.0.120487
None in this release.
Version 26.2.0.119303
Databases
PostgreSQL version 13 is not supported anymore.
2016 MSSQL Server 13.0 is not supported anymore.
Kubernetes
Kubernetes versions 1.30 and 1.31 are not supported anymore.
Version 26.1.0.118079
Java 17 not supported any more
Java version 21 is the minimum version required to run SonarQube Community Build.
Version 25.12.0.117093
Deprecation of Java 17 as a scanner runtime
Java 17 is deprecated as a supported scanner runtime environment and its support ends in July 2026. There is no impact for this change if you use JRE auto-provisioning, enabled by default on scanners that support it, because it keeps Java version requirements always up to date. If you disable JRE auto-provisioning or your scanner doesn’t support it, you need to update to Java 21 or newer. See:
Community post for more information about the deprecation.
Version 25.11.0.114957
None in this release.
Version 25.10.0.114319
Java 17 for SonarQube Community Build instance
Java 17 for running SonarQube Community Build instances is deprecated and will be dropped soon. Java 21 should be used.
Version 25.9.0.112764
None in this release.
Version 25.8.0.111929
None in this release.
Version 25.7.0.110598
Deprecated rules
The following Java and Kotlin rules are now deprecated:
S6291 - Using unencrypted databases in mobile applications is security-sensitive
S6300 - Using unencrypted files in mobile applications is security-sensitive
Version 25.6.0.109173
Mercurial SCM is not supported
The Community plugin for Mercurial SCM is no longer compatible with SonarQube Server.
Sonar Plugin API
The following deprecated classes have been removed: MutableModuleSettings and MutableProjectSettings.
Version 25.5.0.107428
None in this release.
Version 25.4.0.105899
Removed ProfileExporter and ProfileImporter extension points
Removed two extension points in the plugin-api ProfileExporter and ProfileImporter. The following APIs have been deprecated:
GET /api/qualityprofiles/exportAPI endpoint. You can now useGET /api/qualityprofiles/backupinstead.GET /api/qualityprofiles/exportersGET /api/qualityprofiles/importers
See Web API for more information.
Version 25.3.0.104237
None in this release.
Version 25.2.0.102705
Removed sonar.password property
The sonar.password scanner property that was deprecated in SonarQube Server 9.8 has now been removed.
Removed password hash
The BCrypt hash method used for passwords was deprecated in SonarQube Server 8.9. It has now been removed. As a result, the passwords of users who have not logged in since SonarQube 8.9 are deactivated and an admin must reset them if these users need to log in again.
Version 25.1.0.102122
Deprecation of property encryption on the scanner side
Property encryption on the scanner side is now deprecated.
Removed complexity metrics
The following complexity metrics, which were deprecated in SonarQube Server 6.7, have now been removed:
file_complexitycomplexity_in_classesclass_complexitycomplexity_in_functionsfunction_complexityfunction_complexity_distributionfile_complexity_distribution
Version 24.12.0.100206
None in this release.
Full release notes
Latest release version 26.11.0.134175 full release notes in Jira.
Last updated
Was this helpful?

