feature(ci): improvements to ghcr image management#26
Merged
Conversation
Disabled SBOM/provenance embedding and stopped uploading build attestations. Those were creating untagged OCI referrers in GHCR. Still sign with cosign with signatures as referrers.
Contributor
|
Great work @DragonStuff thank you! |
Peyochanchan
referenced
this pull request
in Peyochanchan/once-campfire
Apr 13, 2026
feature(ci): improvements to ghcr image management
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.
I took some time to really optimize how images are being used for the project, in preparation for your upcoming release.
After some tweaking, I've gotten attestations except for the primary attestation to only appear on the Actions -> Attestations and GHCR's "view all versions" tab, reduced the number of images, prevented duplicate CI runs on cut releases / tags, and improved when
:latestwill be pushed (it will only be pushed on a tag). It is possible to remove signatures entirely, but for software BOMs it's kinda essential and allows you to revoke and prevent downstream consumers from using a compromised artifact.After:
From testing in: https://github.com/alexandernicholson/once-campfire/pkgs/container/once-campfire.
Of course as always, let me know what you think and if there are any suggestions!