ci(release): disable provenance/sbom attestations#55
Closed
trick77 wants to merge 1 commit into
Closed
Conversation
docker/build-push-action@v7 attaches SLSA provenance + SBOM attestations
by default; GHCR stores them as extra manifests in the manifest list and
shows them in the UI as 'unknown/unknown' platform. Without an attestation
consumer this is pure noise for triagers ("which image is the real one?").
Skip both. Real architectural manifests stay as they are.
Owner
Author
|
Closing — provenance + SBOM stay enabled. The 'unknown/unknown' GHCR UI entry is cosmetic noise; the supply-chain signals are worth keeping. |
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
Each release currently produces an extra GHCR manifest tagged `unknown/unknown` because `docker/build-push-action@v7` attaches SLSA provenance + SBOM attestations by default. Without a consumer this is pure UI noise. Disable both.
Test plan