ROX-34488: discover cosign signatures via OCI 1.1 Referrers API#21908
Draft
stehessel wants to merge 1 commit into
Draft
ROX-34488: discover cosign signatures via OCI 1.1 Referrers API#21908stehessel wants to merge 1 commit into
stehessel wants to merge 1 commit into
Conversation
|
Skipping CI for Draft Pull Request. |
Contributor
🚀 Build Images ReadyImages are ready for commit fa3f8b2. To use with deploy scripts: export MAIN_IMAGE_TAG=4.12.x-578-gfa3f8b2393 |
stehessel
force-pushed
the
ROX-34488/1-proto-schema
branch
from
July 23, 2026 14:32
06d70e8 to
7a70480
Compare
stehessel
force-pushed
the
ROX-34488/2-referrer-discovery
branch
2 times, most recently
from
July 23, 2026 14:49
4fecac8 to
ea85a49
Compare
stehessel
force-pushed
the
ROX-34488/1-proto-schema
branch
from
July 23, 2026 15:55
7a70480 to
3459544
Compare
stehessel
force-pushed
the
ROX-34488/2-referrer-discovery
branch
3 times, most recently
from
July 23, 2026 17:19
17ac497 to
cebd12e
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## ROX-34488/1-proto-schema #21908 +/- ##
=========================================================
Coverage 51.35% 51.35%
=========================================================
Files 2857 2858 +1
Lines 178796 178891 +95
=========================================================
+ Hits 91822 91876 +54
- Misses 78936 78971 +35
- Partials 8038 8044 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Extract signature payload fetching into cosign_payload_fetcher.go and add referrer-based discovery alongside the existing tag-based method. FetchSignatures now queries both paths and merges results. Referrer errors are swallowed so registries without OCI 1.1 support keep working. This enables discovery of signatures created by cosign v3+, which defaults to storing signatures as OCI referrers instead of legacy tags. Partially generated by AI.
stehessel
force-pushed
the
ROX-34488/2-referrer-discovery
branch
from
July 23, 2026 20:30
cebd12e to
fa3f8b2
Compare
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.
Description
Extract signature payload fetching into
cosign_payload_fetcher.goand add referrer-based discovery alongside the existing tag-based method.FetchSignaturesnow queries both paths and merges results. Referrer errors are swallowed so registries without OCI 1.1 support keep working.This enables discovery of signatures created by cosign v3+, which defaults to storing signatures as OCI referrers instead of legacy tags.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Unit tests for tag-based and referrer-based payload fetching in
cosign_payload_fetcher_test.goandcosign_sig_fetcher_test.gousing an in-memory registry.