Chore: Update to SLSA v1 provenance #968
Merged
Conversation
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
moby/buildkit#6005 Signed-off-by: Brandon Mitchell <git@bmitch.net>
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.
Fixes issue
Describe the change
Update to SLSA v1 provenance in buildkit. See moby/buildkit#6005 for more details.
How to verify it
After merging and GHA finishes, with a buildkit version of 0.23 or greater, the following should now show a full SLSA v1 attestation:
regctl artifact get --platform local --filter-artifact-type application/vnd.docker.attestation.manifest.v1+json --subject ghcr.io/regclient/regctl:edgeNote, the current buildkit version in GHA is still v0.22.0.
Changelog text
Please verify and check that the pull request fulfills the following requirements