The release that goes to the hosts: v1.0.1 plus the quinn-proto patch moved forward to the head of upstream's 0.11.x branch. No change to volto's own code, configuration or scripts since v1.0.1, and v1.0.1 was not deployed.
Changed
- The
quinn-protopatch now points ata708a97, the 0.11.x head of 2026-09-07, sixteen commits past the previous rev. The ones on this proxy's path: the DATAGRAM send buffer series backported in quinn-rs/quinn#2844, where the free space is measured by the queue's real memory use and the queue is pruned for the incoming datagram before it is queued, which is the predicate the CONNECT-UDP session already writes when it grades an eviction; queued DATAGRAMs pruned when the active path changes (#2849); no duplicate flow-control credit for a stopped stream (#2848); DATA_BLOCKED and STREAM_DATA_BLOCKED sent when blocked by flow control (#2852); a DATAGRAM at the exact payload limit retained rather than dropped. The patch stays until a 0.11.x release carries the MTU discovery fixes; crates.io is still at 0.11.17.
Testing
- The moved rev passed the full suite, clippy, rustdoc and both interop suites with
--locked, so the lock files are exactly what was tested. The re-resolutioncargo update -pperforms on the patched crate's whole subtree was read line by line and one unrelated edge it moved was put back.
Upgrading: volto-deploy on the host, or the install line below. No configuration change. Everything in the v1.0.1 notes applies here as well, since this is the first of the two releases to reach a host: a deployment that dials 64:ff9b:1::/48 destinations needs allow_private_networks = true from v1.0.1 on.
Static musl builds for x86_64 and aarch64. Verify with SHA256SUMS.
Each archive carries the binary, LICENSE, README.md and the script/ and docs/ directories. Installing and updating is described in docs/deployment.md.
Full Changelog: v1.0.1...v1.0.2