-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Prepare 0.12 release #2188
Merged
Merged
Prepare 0.12 release #2188
Conversation
This file contains 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
This is a big and breaking change. A lot of the internals were worked on. But the breakage shouldn't be that visible to public API. The main differences are: - Publicly exposes `http` v1, instead of v0.2. - Integration with `hyper::Body` has changed. Co-authored-by: =?UTF-8?q?Lo=C3=AFs=20Postula?= <[email protected]> Co-authored-by: Jakub Wieczorek <[email protected]>
2 tasks
seanmonstar
force-pushed
the
0.12-dev
branch
2 times, most recently
from
March 20, 2024 15:26
87cd4c5
to
8d11890
Compare
Technically a breaking change, since disabling default options will mean HTTP/2 is no longer enabled, and in 0.11.x, it was.
In `Cargo.toml`, hide all optional dependencies as features Currently, reqwest publishes all optional dependencies as features - which is usually not what is intended. Instead, the features should be explicitly declared, whereas optional features are enabled with the new `dep:*` syntax. Note that I also had to fix a few conditional compilations which used optional crates rather than features as conditionals. Also, note the use of the `...?/...` syntax instead of `.../...` -- as this both enabled an optional crate AND adds a feature to it. Now, it uses the `"dep:...", "...?/..."` syntax to prevent exposing crate name. Technically, this is *breaking change*, since people may have enabled some of these features accidentally. That's why we're including it in 0.12.
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.
No description provided.