Release tracking PR: bitreq v0.3.0
#459
Merged
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
TheBlueMatt
force-pushed
the
2026-01-bitreq-0.3
branch
from
bcc238a to
99482ed
Compare
TheBlueMatt
force-pushed
the
2026-01-bitreq-0.3
branch
3 times, most recently
from
1c0d3cf to
18b4256
Compare
Member
|
Yep, lets do it. Can you add a changelog entry please. I wrote this up if you want it. # 0.3.0 - 2026-01-16
* Add support for `native-tls` in addition to `rustls` [#451](https://github.com/rust-bitcoin/corepc/pull/451)
* Support connection reuse and clean up `Connection` [#450](https://github.com/rust-bitcoin/corepc/pull/450)
* Make `async` fetching actually async [#448](https://github.com/rust-bitcoin/corepc/pull/448)
* Remove `urlencoding` dependence [#424](https://github.com/rust-bitcoin/corepc/pull/424)
* Remove `punycode` dependency [#423](https://github.com/rust-bitcoin/corepc/pull/423)
* Remove unused `tokio` features [#421](https://github.com/rust-bitcoin/corepc/pull/421)(I changed the title to help me search later for this later down the track.) |
Sadly `Error` has different fields based on different features, so to avoid downstream crates randomly breaking due to unrelated feature flag settings, we need to mark it `non_exhaustive`.
In the future we'd like to support SOCKS proxies as well, so get ahead of it by renaming `Proxy::new` to `Proxy::new_http` to allow us to have a `Proxy::new_socks5` in a point release.
I believe we should go ahead and release bitreq 0.3 with all the changes we made to it, as its a substantial improvement for async clients and now something that could reasonably be used in place of `reqwest` in most cases. There's some remaining proxy issues, but those can be resolved in a point release without API change.
... in Australian time
TheBlueMatt
force-pushed
the
2026-01-bitreq-0.3
branch
from
18b4256 to
b9db614
Compare
Member
Author
|
Okay, rebased and added changelog entries (with some marginal verbiage tweaks) |
tcharding
approved these changes
Jan 16, 2026
Member
|
BOOM! Thanks man. Tagged and published. |
Member
Author
|
Wohoo, ecosystem migration LFG. If you missed it, breez was looking into using bitreq and it reduced their total binary size by something like 1.5-2.5 MB, which is absolutely insane. |
2 tasks
Member
|
Ah sick, LFG indeed. |
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.
Based on #452 I think its reasonable to release a bitreq 0.3. There's some issues remaining in the proxy code described in #458 but those should be addressable in a point release without API breakage.