feat(ci): add SLSA build provenance attestation to Docker builds#147
Open
feat(ci): add SLSA build provenance attestation to Docker builds#147
Conversation
Add actions/attest-build-provenance step to the shared Docker build workflow, producing SLSA-compatible provenance for all container images pushed to GHCR. Uses continue-on-error since caller workflows need to add attestations:write permission to fully enable this. Ref: platform-mesh/backlog#229 Signed-off-by: Bastian Echterhölter <bastian.echterhoelter@sap.com> On-behalf-of: @SAP <bastian.echterhoelter@sap.com>
This was referenced Apr 11, 2026
Merged
Merged
Merged
Merged
Merged
Caller workflows will have attestations:write before this lands. Signed-off-by: Bastian Echterhölter <bastian.echterhoelter@sap.com> On-behalf-of: @SAP <bastian.echterhoelter@sap.com>
Open
6 tasks
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
actions/attest-build-provenance@v4to the sharedjob-docker-build-push.ymlreusable workflowgh attestation verifycontinue-on-error: trueso existing caller pipelines that haven't addedattestations: writeyet won't breakFollow-up required
Caller workflows (all operator/service pipelines) need to add
attestations: writeto their top-level permissions block for the attestation to succeed. Without it, the step will soft-fail and the image is still built, signed, and pushed as before.Example change in caller pipelines:
Verification
After a caller adds
attestations: writeand merges a build:Ref: platform-mesh/backlog#229