Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
Body
Provide full support for the OCI Distribution Specification 1.1 Referrers API (
GET /v2/<name>/referrers/<digest>).The current fallback mechanism appears to work with clients such as ORAS, but native Referrers API support would provide the standards-compliant approach for discovering artifacts associated with an image, including signatures, attestations, SBOMs, and other OCI artifacts. This should include the relevant OCI-Subject behavior and return the standard OCI Index response.
Ideally, referrers should also be surfaced in the GitHub Container Registry UI, so users can discover and inspect related artifacts without needing ORAS or manually querying the registry. The existing fallback should remain supported for compatibility, but native OCI 1.1 support should be the primary path.
Reference:
https://opencontainers.org/posts/blog/2024-03-13-image-and-distribution-1-1/
All reactions