Open
Conversation
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
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.
Which issue does this PR close?
N/A.
Rationale for this change
OpenDAL still depends on
reqwest 0.12.x, while the currentreqwest 0.13.xline changes the rustls feature name and simplifies the TLS defaults. This updates the core dependency chain toreqwest 0.13.2and removes the tracing dev-dependency path that was still pullingreqwest 0.12viaopentelemetry-otlpdefaults.What changes are included in this PR?
This PR bumps
reqwestto0.13.2inopendal-coreand the top-levelcorecrate, updates the internalreqwest-rustls-tlsfeature mapping toreqwest/rustls, disables default features for the tracing layer'sopentelemetry-otlpdev-dependency sogrpc-tonicdoes not reintroducereqwest 0.12, and refreshes the reqwest docs links in the HTTP optimization guide.Are there any user-facing changes?
Users building against OpenDAL's reqwest-backed HTTP client will now resolve
reqwest 0.13.xinstead of0.12.x. The public API and documenteddns_resolver(...)usage remain unchanged.AI Usage Statement
AI-assisted editing and review were used while preparing this PR.