Upgrade Sozu to 2.2.0 - #124
Merged
Merged
Conversation
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
1 participant
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.
Upgrades Sozu from 2.1.0 to 2.2.0.
What comes with it
2.1.1 : WebSocket fixes in the
pipelayer (symmetric write rearming, byte preservation after upgrade, restored upgrade readiness) and a security bump for RUSTSEC-2026-0190.2.2.0 : SNI+ALPN ClientHello preread passthrough routing (#1279), HTTP/1
Transfer-Encodingframing hardening (reopens #726), kawa 0.7.1. MSRV raised to 1.91, which our pinned Rust 1.95.0 already satisfies.Why the lockfile diff is large
No application code changed, the source diff is two lines. Sozu 2.2.0 raises three version floors (
log^0.4.33,mio^1.2.2,rustls^0.23.42) that the lockfile pinned lower, so resolution needed a globalcargo update. That also pulled wasmtime and the wit-bindgen tree forward, hence 460/-645 inCargo.lock.Constraining the update to only the required crates was possible but more fragile.
Note on rustls backends
cheti pulls
rustlswith theringbackend while Sozune declaresaws-lc-rs, so both providers now coexist in the binary. Not a problem:install_default()is called explicitly onaws_lc_rsat both TLS entry points (src/acme/mod.rs:328,src/provider/kubernetes/mod.rs:111). Pre-existing, not introduced here.Follow-up
The 2.2.0 SNI+ALPN preread unblocks three board items, to be handled in separate PRs:
TCP routing with SNI,Gateway API: TLSRoute, andTLS-ALPN-01 challenge.