Test: verify publish check catches provenance issue#634
Closed
Test: verify publish check catches provenance issue#634
Conversation
Cherry-pick the publish_check workflow WITHOUT the --provenance=false fix. This PR should fail at the "Validate digests" step, proving the check catches the manifest list issue. See #633.
Contributor
Author
|
Check fails as expected, closing PR. |
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.
Purpose
Verify that the publish check workflow from #633 actually catches the buildx provenance/manifest list issue. This PR has the workflow but NOT the
--provenance=falsefix.Expected result
The "Validate digests for manifest compatibility" step should fail with "is a manifest list", proving the check works. Do not merge — close after verifying.