ci: SLSA build-provenance attestation at release (#208, partial) - #309
Merged
Conversation
Adds an actions/attest-build-provenance step to the release's update-release-artifacts job: each packed .nupkg gets a signed, verifiable SLSA provenance statement (built by this repo's release.yaml, from a specific commit), stored in the repo's attestation store. Grants the job id-token:write + attestations:write for it. Complements the CycloneDX SBOM already shipped. SECURITY.md gains a "Verifying the supply chain" section documenting how a consumer verifies the SBOM + attestation (`gh attestation verify <pkg> --repo Chris-Wolfgang/ETL-Abstractions`), and explicitly flags that Authenticode/NuGet package signing is NOT yet enabled. Partial for #208: SBOM (already) + SLSA attestation are done; package signing (`nuget verify`-able signatures) still needs a code-signing certificate and stays open on #208. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jul 24, 2026
This was referenced Aug 5, 2026
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
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
Adds SLSA build provenance to the release (issue #208). The
update-release-artifactsjob now runsactions/attest-build-provenanceon each packed.nupkg— recording a signed, verifiable statement that the artifact was built by this repo'srelease.yamlfrom a specific commit, stored in the repo's attestation store. The job gainsid-token: write+attestations: writefor it (action SHA-pinned per the zizmorhash-pinpolicy).SECURITY.mdgains a "Verifying the supply chain" section documenting how a consumer verifies the artifacts:and explicitly notes what's not yet done.
Scope vs #208 — partial (intentionally not
Closes)bom.json)nuget verify)SECURITY.mdverification procedureSo #208 stays open for the signing half. If you have (or want to provision) a code-signing cert + secret, I can add the
dotnet nuget signstep as a follow-up.Validation
hash-pin) + actionlint clean on the modifiedrelease.yaml.Relates to #208 (does not close it).