Skip to content

ci(release): mark the generator's tag reference as deliberate for SonarCloud #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mescon merged 1 commit into from
Sep 15, 2026
Merged

ci(release): mark the generator's tag reference as deliberate for SonarCloud #104

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .github/workflows/publish-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -708,8 +708,9 @@ jobs:
contents: write # attaches the statement to the release
# Referenced by tag, not by commit hash, on purpose: slsa-verifier can
# only verify the generator's ref when it is a tag (the generator's
# README, "Referencing SLSA builders and generators").
uses: slsa-framework/slsa-github-generator/.github/workflows/generator_generic_slsa3.yml@v2.1.0
# README, "Referencing SLSA builders and generators"). The marker
# below tells SonarCloud's pin-by-hash rule that this one is deliberate.
uses: slsa-framework/slsa-github-generator/.github/workflows/generator_generic_slsa3.yml@v2.1.0 # NOSONAR the SLSA generator must be referenced by tag
with:
base64-subjects: ${{ needs.hashes.outputs.hashes }}
provenance-name: release-assets.intoto.jsonl
Expand Down
Loading