Disabled Rules in Inherited Quality Profiles Re-Activating After Upgrade

Hi,
we am encountering an issue with inherited quality profiles in SonarQube. We have disabled certain rules in an inherited quality profile to suit our project’s needs. However, after upgrading SonarQube to a newer version, these rules are reactivated, which disrupts our analysis.
Is this expected behavior? If so, is there a recommended way to persist the customization of inherited quality profiles across upgrades?
I’d appreciate any advice or guidance on how to address this issue.

We are running Sonarqube Developer Edition in a docker container. This behaviour occurs quite often (maybe even with all upgrades), the following screenshot shows an example for an upgrade from 10.8.0 to 10.8.1

In the screenshot you can e.g. see that on Dec 13th we manually disabled the “React props should be read-only” rule, but the upgrade from 10.8.0 to 10.8.1 re-activates the rule

Thanks in advance!

Best regards,
Lukas

Hey there @Lukas_Haselsteiner

Yikes! I can reproduce this on an upgrade from 10.8.0 to 10.8.1 on a profile that uses the built-in Sonar Way as its parent profile.

I’ve flagged this for attention.

A dear colleague just pointed me to the existing ticket. :slight_smile: SONAR-23184

Thanks! Looking forward to a fix for this :crossed_fingers: