Bug-fix release for SonarQube Community edition. No new resources; no breaking changes.
Fixes
- fix: read project-level new code periods from the main branch on Community by @Cesarsk in #407 — Community has no project-level new code period: SonarQube stores a project-level setting on the main branch and keeps reporting the inherited
PREVIOUS_VERSIONdefault for the project. A project-levelsonarqube_new_code_periodswith any other type (NUMBER_OF_DAYS,REFERENCE_BRANCH) therefore showed a diff on every plan that applying never settled. Read now falls back to the main branch when the project-level value is inherited. Developer edition and above are unaffected.
Upgrading
On Community, the first plan after upgrading no longer shows those diffs. Nothing changes in SonarQube.
Full Changelog: v0.16.24...v0.16.25