Bump hyper-util from 0.1.20 to 0.1.21 in /python/rust

[dependabot]

Bumps hyper-util from 0.1.20 to 0.1.21.

Release notes

Sourced from hyper-util's releases.

v0.1.21

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.

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.

... (truncated)

Changelog

Sourced from hyper-util's changelog.

0.1.21 (2026-09-24)

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.

Commits

• 23a8689 v0.1.21
• cdb2346 doc(client/pool): add broken_intra_doc_links allowance (#326)
• 13b6110 chore(error): remove disabled hyper_util::error submodule (#325)
• b9ee451 docs(lib): add crate-level documentation (#327)
• d6b7d7e feat(rt/tracing): introduce tracing executors (#323)
• f2da915 feat(client): add HttpConnector::set_mark for SO_MARK (#303)
• 4dbd494 feat(rt): change TokioExecutor to not trace, add rt-tracing-exec-force feat...
• d480d9f fix(client): parse proxy CONNECT response with httparse (#315)
• 7e0958b chore(ci): simplify msrv check (#317)
• 0734568 chore(ci): update to actions/checkout@v7 (#316)
• Additional commits viewable in compare view

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.