Remove provenance/sbom from Docker image action - #2251
Merged
Merged
Conversation
in the hope of removing "unknown/unknown" architectures from the GitHub packages interface. Incidentally update the changelog for release v2.25.2 .
|
Sure, this removed the "unknown/unknown", but IMO this is not the correct way of tackling the problem, as provenance (SBOM) can be useful and "unknown/unknown" is just the presentation problem of GHCR. |
Contributor
Author
|
@stefanb I'm happy to put those back if they are useful to you! |
3 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
2 participants
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.
Description
Remove provenance/sbom from Docker image action, in the hope of removing "unknown/unknown" architectures from the GitHub packages interface.
Incidentally update the changelog for release v2.25.2 .
Checklist
changelog.mdfile.AUTHORSfile (or it's already there).