ci: sign published images (cosign) + attest SLSA build provenance#40
Merged
Conversation
…enance Images pushed to ghcr.io were unsigned with no provenance. Add keyless cosign signing of the pushed image by digest (OIDC, no keys) and an actions/attest-build-provenance SLSA provenance attestation pushed to the registry. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
The
Docker publishworkflow pushed the release image toghcr.iowith no signature and no provenance. This adds supply-chain attestation to the published image:actions/attest-build-provenance, pushed to the registry as an attestation.Adds
id-token: write+attestations: writepermissions and signs the immutable digest (not the mutable tag). Consumers can verify withcosign verify/gh attestation verify.Note: the new actions use major-version tags to match this workflow's existing convention (
@v7,@v4); pinning all actions to commit SHAs is a repo-wide follow-up.Closes part of the agentrust-io supply-chain hardening (catalog Appendix B, "artifact signing / SLSA provenance").
🤖 Generated with Claude Code