chore: refactor fetch calls to be more oras compatible - #201
Merged
Conversation
brandtkeller
previously approved these changes
Jul 24, 2026
brandtkeller
left a comment
brandtkeller
left a comment
Member
There was a problem hiding this comment.
Discussed migrating some of the root pinning work here as well as potential to make OrasRemote a ReadOnlyTarget as well. I won't block on testing changes but can re-approve in short order if updated.
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
This migrates the OCI references to be compatible with ORAS' content Fetcher interface which allows it to be used more directly in downstream ORAS Go library calls.
Related Issue
Fixes #N/A