Conversation
MFSGA
force-pushed
the
renovate/hyper-util-0.x-lockfile
branch
from
September 24, 2026 20:57
521f94b to
326ed30
Compare
MFSGA
force-pushed
the
renovate/hyper-util-0.x-lockfile
branch
from
September 25, 2026 20:54
326ed30 to
57dd757
Compare
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.
This PR contains the following updates:
0.1.20→0.1.21Release Notes
hyperium/hyper-util (hyper-util)
v0.1.21Compare Source
This release bumps the minimal supported Rust version (MSRV) from 1.64 to 1.85.
This release bumps the rust edition from 2021 to 2024.
Additions
client::legacy::Builder::http2_header_table_size()method. (#274)client::legacy::Builder::http2_max_concurrent_streams()method. (#274)client::legacy::Builder::http2_max_local_error_reset_streams()method. (#277)client::legacy::connect::HttpConnector::set_mark()method. (#303)rt::tracing::WithSpanExecutor<E>,hyper_util::rt::tracing::CurrentSpanExecutor<E>, andhyper_util::rt::tracing::MkSpanExecutor<E, F>executors. (#323)Fixes
client::legacy::Clientso that it properly validates CONNECT responses. (#315)client::legacy::Clientto cancel the idle interval once its pool empties. (#292)client::legacy::Clientto properly handle IPv6 addresses when using a SOCKS proxy. (#302)client::pool::cacheto preserve readiness with clones. (#297)client::pool::cacheto wake its waiters in FIFO order. (#298)client::pool::singleton::Singletonto properly handle cancellation. (#299)client::pool::singleton::Singletonto share errors with all waiters. (#296)client::proxy::matcherhandling for IP wildcards. (#309)tokio/netfeature is narrowed to theclient-legacyfeature flag, from theclientfeature flag. (#276)client::legacy::Client's SOCKS proxying. (#302) (#307) (#308) (#310)Changes
This release contains a minor behavioral change for users of the
tracingfeature flag to be aware of.
This feature flag was introduced in v0.1.11. When enabled,
rt::TokioExecutor<E>began propagating the currently activetracing::Spanto spawned tasks when
hyper::rt::Executor::execute()is called. This causedissues for some users, due to background tasks keeping a span open for the
duration of a long-lived connection.
This behavior has now been removed from
rt::TokioExecutor<E>(#322) by default. A
collection of executor wrappers have been added to a new
rt::tracingsubmodule, to provide facilities for instrumenting a client or server's spawned
tasks. See the module-level documentation of
rt::tracingfor moreinformation.
To temporarily preserve the previous
rt::TokioExecutor<E>span propagationbehavior, enable the
rt-tracing-exec-forcefeature. Note that this featureflag will be removed in a future release.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.