ci: reference slsa-github-generator by tag (fix exit 127 / missing provenance)#6
Merged
Conversation
The slsa-github-generator reusable workflow downloads its builder binary from the release matching its own ref. SHA-pinning it means there is no matching release to resolve, so the binary is never fetched and the attest step dies with exit 127 (No such file or directory), leaving an empty provenance that fails the upload-assets and final jobs. Pin by the v2.1.0 tag (documented requirement); a comment records why this is an explicit exception to the SHA-pinning policy.
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.
Summary
@v2.1.0tag.Why
Both
v0.1.0-rc.1andv0.1.0-rc.2dry-runs failed the SLSA jobs identically. Root cause: theslsa-github-generatorreusable workflow downloads its builder binary from the release matching its own ref. When pinned by a 40-char SHA there is no matching release, the binary is never fetched, and the attest step dies withexit 127(slsa-generator-generic-linux-amd64: No such file or directory) — leaving an empty provenance that failsupload-assetsandfinal.Referencing by the semver tag is the project's documented requirement; the generator self-verifies the downloaded builder against the release. A code comment records this as an explicit, justified exception to the repo's SHA-pinning policy.
Test plan
v0.1.0-rc.3→ all SLSA jobs (generator,upload-assets,final) pass andmultiple.intoto.jsonlis attached to the prerelease.