Deprecations and removals

This page contains information on the deprecation and removal of SonarQube Community Build features and API endpoints.

• Each deprecated feature or API endpoint will be removed in a future release. We recommend to start using its replacement (if any) as soon as possible.
• Plugin API deprecations are announced in the sonar-plugi-api GitHub repository.

Deprecation time frame

A deprecated feature can be dropped in the year following the year it was deprecated, with a minimum of 6 months after deprecation.

For example, a feature deprecated in the 25.3 Community Build can be removed starting in the 26.1 Community Build.

A backward-incompatible change or dropping of a public API endpoint, a workflow, or a feature is subject to the deprecation. Once deprecated, it will be removed in a future version.

SonarQube Community Build 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

SonarQube Community Build 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_complexity
• complexity_in_classes
• class_complexity
• complexity_in_functions
• function_complexity
• function_complexity_distribution
• file_complexity_distribution

SonarQube 10.6

Deprecated build wrapper output property

• Announced in SonarQube 10.6 (June 2024)
• Removal in SonarQube 11.0 or later

Build Wrapper collects information from the build in two separate JSON formats: compile_commands.json and build-wrapper-dump.json. Both these files are generated in the specified output directory. The build-wrapper-dump.json format and its associated property sonar.cfamily.build-wrapper-output are deprecated. The sonar.cfamily.compile-commands property should be used instead to specify the path to the compile_commands.json file.

Additional API updates

When querying rules or issues, INFO and BLOCKER may appear as statuses at the quality level (i.e. a rule might have a reliability severity of BLOCKER). It is also possible to create rules/issues with these additional severities. 

The affected APIs:

• api/issues/*
• api/rules/*
• api/projects/export_findings
• api/qualityprofiles/compare
• api/qualityprofiles/changelog