Skip to content

chore(deps): update rust crate hyper-util to v0.1.21 - #75

Open
MFSGA wants to merge 1 commit into
mainfrom
renovate/hyper-util-0.x-lockfile
Open

MFSGA wants to merge 1 commit into
mainfrom
renovate/hyper-util-0.x-lockfile

Conversation

@MFSGA

@MFSGA MFSGA commented Sep 24, 2026

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
hyper-util (source) dependencies patch 0.1.20 → 0.1.21

Release Notes

hyperium/hyper-util (hyper-util)

v0.1.21

Compare 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

  • Add crate-level documentation. (#​327)
  • Add client::legacy::Builder::http2_header_table_size() method. (#​274)
  • Add client::legacy::Builder::http2_max_concurrent_streams() method. (#​274)
  • Add client::legacy::Builder::http2_max_local_error_reset_streams() method. (#​277)
  • Add client::legacy::connect::HttpConnector::set_mark() method. (#​303)
  • Add rt::tracing::WithSpanExecutor<E>, hyper_util::rt::tracing::CurrentSpanExecutor<E>, and hyper_util::rt::tracing::MkSpanExecutor<E, F> executors. (#​323)

Fixes

  • Fix client::legacy::Client so that it properly validates CONNECT responses. (#​315)
  • Fix client::legacy::Client to cancel the idle interval once its pool empties. (#​292)
  • Fix client::legacy::Client to properly handle IPv6 addresses when using a SOCKS proxy. (#​302)
  • Fix client::pool::cache to preserve readiness with clones. (#​297)
  • Fix client::pool::cache to wake its waiters in FIFO order. (#​298)
  • Fix client::pool::singleton::Singleton to properly handle cancellation. (#​299)
  • Fix client::pool::singleton::Singleton to share errors with all waiters. (#​296)
  • Fix client::proxy::matcher handling for IP wildcards. (#​309)
  • The tokio/net feature is narrowed to the client-legacy feature flag, from the client feature flag. (#​276)
  • Various fixes to the client::legacy::Client's SOCKS proxying. (#​302) (#​307) (#​308) (#​310)

Changes

This release contains a minor behavioral change for users of the tracing
feature flag to be aware of.

This feature flag was introduced in v0.1.11. When enabled,
rt::TokioExecutor<E> began propagating the currently active tracing::Span
to spawned tasks when hyper::rt::Executor::execute() is called. This caused
issues 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::tracing
submodule, to provide facilities for instrumenting a client or server's spawned
tasks. See the module-level documentation of rt::tracing for more
information.

To temporarily preserve the previous rt::TokioExecutor<E> span propagation
behavior, enable the rt-tracing-exec-force feature. Note that this feature
flag will be removed in a future release.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@MFSGA
MFSGA force-pushed the renovate/hyper-util-0.x-lockfile branch from 521f94b to 326ed30 Compare September 24, 2026 20:57
@MFSGA
MFSGA force-pushed the renovate/hyper-util-0.x-lockfile branch from 326ed30 to 57dd757 Compare September 25, 2026 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants