Deprecations and removals

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

Deprecation time frame

When a deprecation is announced here, it marks the start of the deprecation time frame. The feature or API endpoint will be removed anytime after the time frame expires.

• Feature deprecation is announced at least 90 days before the feature is removed.
• API endpoint deprecation is announced at least 180 days before the endpoint is removed.

A backward-incompatible change or dropping of a public API endpoint, a workflow, or a feature can be considered deprecation. Once deprecated, they will be removed after a defined period of time.

Deprecation announcements

Deprecated build wrapper output property

• Announced in May 2024
• Removal after July 10 2024

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