SonarCloud: bump projectVersion to 0.2 to baseline the Phase 2 sprint - #22
Merged
Conversation
The project's new-code period is "previous version", so with version 0.1 set at the very first analysis the whole sprint has counted as new code and the 80% new-code coverage condition has measured the entire frontend, whose React components have no tests (66.5% after lcov started reporting branches). From the next analysis on main, 0.2 is the baseline and the gate applies only to changes from here on. Overall coverage stays visible. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
SonarCloud analysis · PR #22Quality gate: ✅ Passed · Open in SonarCloud
Open issues on new code: 0No open issues on the changed code. 🎉 Commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
One-line change to
sonar-project.properties:sonar.projectVersion0.1 to 0.2.Why
The project's new-code period is "previous version" (confirmed via the settings API). Version 0.1 was set at the very first analysis, so the entire Phase 2 sprint has counted as new code and the 80% new-code coverage condition has been measuring the whole frontend. Now that vitest reports lcov with branch data (PR #21), that figure is an honest 66.5%: the React components have no tests and contribute 375 uncovered branches.
Per Dan's call, the sprint becomes the baseline. From the next analysis on
main, the coverage gate applies only to changes from here on. Overall coverage stays visible on the project dashboard, so nothing is hidden.The Python package version (
0.1.0in the health endpoint) is untouched; that is a product decision, not a Sonar one.🤖 Generated with Claude Code