ci: report sonar.projectVersion from package.json for new-code baseline#2
Merged
Conversation
|
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.
The SonarCloud project's new-code definition is set to Previous version, which only resets the baseline correctly if each analysis reports the project version. The scan did not pass
sonar.projectVersion, so the baseline never advanced at releases.This reads the version from
package.json(the single source of truth, kept in sync withcore.tsby sync-version) and passes it to the scanner viaargs: -Dsonar.projectVersion=.... The value is repo-controlled and passed as a scanner arg (not interpolated into a shell command).CI/workflow-only change; no library source touched.