ci(release): mark the generator's tag reference as deliberate for SonarCloud - #104
Merged
Merged
Conversation
…arCloud SonarCloud's pin-by-hash rule fails the quality gate on the SLSA generator line. The generator has to be referenced by tag, or slsa-verifier cannot verify its ref, so the line carries the marker that tells the rule the choice is deliberate, with the reason.
mescon
enabled auto-merge
September 15, 2026 10:31
|
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.
SonarCloud rule S7637 (pin by hash) fails the quality gate on the SLSA generator reference, which must stay a tag for slsa-verifier. This adds the NOSONAR marker with the reason on that line. The SonarCloud check on this PR shows whether the analyzer honours it for workflow files.