hyper-util: Please don't use a version range dependency on socket2

[joshtriplett]

Version

hyper-util 0.1.20

Platform

Linux o 6.19.12+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.19.12-1 (2026-04-13) x86_64 GNU/Linux

Summary

Cargo's version resolver doesn't handle version ranges like this very well, resulting in non-deterministic flip-flopping of versions, or selection of multiple versions of socket2. (For instance, if other crates want the newer version, this range may result in cargo resolving to both the old and new version.)

rust-lang/cargo#9029
rust-lang/cargo#5529
https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/Cargo.2Elock.20non-deterministically.20flipflopping/with/520024108

Please consider depending exclusively on the new version of socket2.

I saw the mention that you want your MSRV to support Debian stable. Debian stable currently has 1.85, which works with latest socket2.

[seanmonstar]

Has this caused issues specifically, or it just could be an issue?

[joshtriplett]

@seanmonstar I ran into this because I upgraded to new hyper-util and started getting non-deterministic resolution of socket2 versions.

[cratelyn]

• https://github.com/linkerd/linkerd2-proxy/pull/4501/changes#diff-13ee4b2252c9e516a0547f2891aa2105c3ca71c6d7a1e682c69be97998dfc87eR1041
• https://github.com/linkerd/linkerd2-proxy/pull/4478/changes#diff-13ee4b2252c9e516a0547f2891aa2105c3ca71c6d7a1e682c69be97998dfc87eR1041

seconding that we also see this "flapping" when taking in dependabot updates in the linkerd2 proxy.

[seanmonstar]

Amazing! Well, ok then.