ci(release): sign every asset and attach SLSA provenance - #101
Merged
Merged
Conversation
The signing job only ever covered the Arch packages and their repository database, although the README and the assurance document said every asset was signed; the Debian packages, the telemetry helpers and the SBOMs went out bare. The release workflow now ends with three jobs that run once every asset is attached: one signs every asset that has no detached signature yet with the same key, one hashes the whole asset list, and one hands the list to the SLSA generic generator, which signs a build provenance statement through Sigstore and attaches it as release-assets.intoto.jsonl. slsa-verifier can then confirm an asset against the repository and the tag. The generator is referenced by tag because slsa-verifier cannot verify its ref otherwise. A provenance-only dispatch input skips every channel and exercises the provenance jobs against an existing release without uploading anything, which is how the jobs get tested before the next release. The docs now say what was signed up to 0.41.0 instead of overstating it.
mescon
enabled auto-merge
September 14, 2026 21:02
|
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.
Three jobs at the end of the release workflow: sign every asset without a detached signature (the old job covered only the Arch packages and the repo database, contrary to what the docs said), hash the whole asset list, and attach a SLSA provenance statement (
release-assets.intoto.jsonl) signed through Sigstore by the SLSA generic generator v2.1.0. Adds aprovenance-onlydispatch input so the provenance jobs can be exercised against an existing release without uploading. Linted with actionlint (no new findings). Docs corrected to say what was signed up to 0.41.0.Scorecard: Signed-Releases goes from 8 to 10 per release that carries provenance; the generator is referenced by tag (required by slsa-verifier), which Pinned-Dependencies will note.