Repository navigation
feat(ci): attest build provenance - #77
Merged
Merged
Conversation
Estate artifact-attestation rollout mirroring the proven exemplar. Attests: container image (publish-container.yml) + release binaries artifacts/**/* + SHA256SUMS.txt (release.yml).
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.
Build-provenance attestation
Adds GitHub native build-provenance attestation (
actions/attest-build-provenance@e8998f94…# v2) to the release pipeline, mirroring the proven estate exemplar.Attested artifacts
publish-container.yml: attestsghcr.io/${{ github.repository }}by digest from thedocker/build-push-actionpush step (push-to-registry: true). Added job-levelid-token: write+attestations: writepermissions andid: pushto the build step.release.yml: attestsartifacts/**/*+SHA256SUMS.txt(the downloaded build artifacts and checksums) after the softprops release step. Addedid-token: write+attestations: writeto thereleasejob (keptcontents: write).Out of scope / skipped
ghcr-publish.yml— builds/pushes via nerdctl, which has no clean digest output suitable for attestation. Thedocker/build-push-actionpath inpublish-container.ymlalready covers container attestation, so this workflow is intentionally left untouched.publish-*.ymlfiles (cargo/npm/scoop/etc.) — package registries, out of scope.YAML validated with
yaml.safe_load. Do not merge yet.