uv
a5fd3d9c - Update Rust crate hyper-util to v0.1.21 (#22923)

Commit
7 days ago
Update Rust crate hyper-util to v0.1.21 (#22923) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [hyper-util](https://hyper.rs) ([source](https://redirect.github.com/hyperium/hyper-util)) | workspace.dependencies | patch | `0.1.20` → `0.1.21` | --- ### Release Notes <details> <summary>hyperium/hyper-util (hyper-util)</summary> ### [`v0.1.21`](https://redirect.github.com/hyperium/hyper-util/blob/HEAD/CHANGELOG.md#0121-2026-09-24) [Compare Source](https://redirect.github.com/hyperium/hyper-util/compare/v0.1.20...v0.1.21) 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. ([#&#8203;327](https://redirect.github.com/hyperium/hyper-util/pull/327)) - Add `client::legacy::Builder::http2_header_table_size()` method. ([#&#8203;274](https://redirect.github.com/hyperium/hyper-util/pull/274)) - Add `client::legacy::Builder::http2_max_concurrent_streams()` method. ([#&#8203;274](https://redirect.github.com/hyperium/hyper-util/pull/274)) - Add `client::legacy::Builder::http2_max_local_error_reset_streams()` method. ([#&#8203;277](https://redirect.github.com/hyperium/hyper-util/pull/277)) - Add `client::legacy::connect::HttpConnector::set_mark()` method. ([#&#8203;303](https://redirect.github.com/hyperium/hyper-util/pull/303)) - Add `rt::tracing::WithSpanExecutor<E>`, `hyper_util::rt::tracing::CurrentSpanExecutor<E>`, and `hyper_util::rt::tracing::MkSpanExecutor<E, F>` executors. ([#&#8203;323](https://redirect.github.com/hyperium/hyper-util/pull/323)) #### Fixes - Fix `client::legacy::Client` so that it properly validates CONNECT responses. ([#&#8203;315](https://redirect.github.com/hyperium/hyper-util/pull/315)) - Fix `client::legacy::Client` to cancel the idle interval once its pool empties. ([#&#8203;292](https://redirect.github.com/hyperium/hyper-util/pull/292)) - Fix `client::legacy::Client` to properly handle IPv6 addresses when using a SOCKS proxy. ([#&#8203;302](https://redirect.github.com/hyperium/hyper-util/pull/302)) - Fix `client::pool::cache` to preserve readiness with clones. ([#&#8203;297](https://redirect.github.com/hyperium/hyper-util/pull/297)) - Fix `client::pool::cache` to wake its waiters in FIFO order. ([#&#8203;298](https://redirect.github.com/hyperium/hyper-util/pull/298)) - Fix `client::pool::singleton::Singleton` to properly handle cancellation. ([#&#8203;299](https://redirect.github.com/hyperium/hyper-util/pull/299)) - Fix `client::pool::singleton::Singleton` to share errors with all waiters. ([#&#8203;296](https://redirect.github.com/hyperium/hyper-util/pull/296)) - Fix `client::proxy::matcher` handling for IP wildcards. ([#&#8203;309](https://redirect.github.com/hyperium/hyper-util/pull/309)) - The `tokio/net` feature is narrowed to the `client-legacy` feature flag, from the `client` feature flag. ([#&#8203;276](https://redirect.github.com/hyperium/hyper-util/pull/276)) - Various fixes to the `client::legacy::Client`'s SOCKS proxying. ([#&#8203;302](https://redirect.github.com/hyperium/hyper-util/pull/302)) ([#&#8203;307](https://redirect.github.com/hyperium/hyper-util/pull/307)) ([#&#8203;308](https://redirect.github.com/hyperium/hyper-util/pull/308)) ([#&#8203;310](https://redirect.github.com/hyperium/hyper-util/pull/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>` ([#&#8203;322](https://redirect.github.com/hyperium/hyper-util/pull/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. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - Between 12:00 AM and 03:59 AM, only on Monday (`* 0-3 * * 1`) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/astral-sh/uv). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODAuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjE4MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJidWlsZDpza2lwLWRvY2tlciIsImJ1aWxkOnNraXAtcmVsZWFzZSIsImludGVybmFsIl19--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Author
Parents
Loading