-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: remove curl fallback #568
Conversation
eb665ef
to
d787152
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the PR description you say "users in this situation need to do X, and other users in other situation need to do Y"
Can we somehow print these as error messages to make it more discoverable?
Good suggestion, some of these are not exactly detectable but we can hint those. I'll see what can be done. |
e62b977
to
d7d1112
Compare
Okay, it's done. |
@alexeagle PTAL again. |
d7d1112
to
97f7b31
Compare
fixes #562
BREAKING CHANGE
Now that curl fallback is gone, users hitting that code path has to do following.
People hitting the curl fallback due to Schema 1 manifest will have to, either upgrade to
Bazel 7.1
or use adigest
instead of atag
for oci_pull.People hitting the curl fallback due to oci-media-typed images being fetched without an
Accept
header will have to, either upgrade toBazel 7.1
, or use aCredential Helper
to set headers expected by the registry, including the authorization headers.