Conversation
Bumps direct dependencies that were several majors behind: - rcgen 0.13 → 0.14 (workspace + tests/streaming dev-dep). Migrates the CertificateParams::signed_by API: leaf certs are now signed against an Issuer instead of taking the (cert, key) pair directly. Uses CertifiedIssuer::self_signed for the CA so the same value yields both the trust-store cert and the signing identity. Also renames the CertifiedKey::key_pair field to signing_key in tests/streaming. - webpki-roots 0.26 → 1 (eliza example). No code changes — the TLS_SERVER_ROOTS API surface is unchanged. - pprof 0.14 → 0.15 (rpc bench harness). No code changes. - rand 0.9 → 0.10 (eliza example). The Rng trait is split into Rng + RngExt in 0.10; random_range moved to RngExt, so the import changes from rand::Rng to rand::RngExt. Pins direct deps to security-advisory floors while preserving the same caret major: - tracing-subscriber 0.3 → 0.3.20 (conformance, eliza, multiservice). RUSTSEC-2025-0055: ANSI escape sequence injection via logged user input. Fixed in 0.3.20. - regex 1 → 1.5.5 (eliza). RUSTSEC-2022-0013: DoS via complex regex parsing. Fixed in 1.5.5. criterion stays at 0.5 because pprof 0.15 still pins criterion ^0.5 for its PProfProfiler integration; bumping criterion past 0.5 would mean giving up the bench-time profiler hook. Many transitive deps refreshed via cargo update — notably tokio 1.49 → 1.50 and hyper 1.8 → 1.9. Cargo.lock is gitignored (library workspace) so the lockfile changes don't show up in this commit. All 37 test results pass; all six conformance suites pass at the expected counts (3600/1192/2396 server, 2580/1454/2838 client).
dfd7f38 to
95f363d
Compare
rpb-ant
previously approved these changes
Apr 2, 2026
rpb-ant
approved these changes
Apr 2, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Bumps direct dependencies that were several majors behind (per deps.rs) and pins direct deps to security-advisory floors while preserving each crate's major caret.
cargo updaterefreshes the rest of the transitives.Direct deps bumped (major)
rcgenwebpki-rootsTLS_SERVER_ROOTSAPI surface unchangedpprofrandRngtrait split intoRng+RngExtin 0.10 —random_rangemoved toRngExt, so the import changes accordinglyrcgen 0.14 migration
CertificateParams::signed_byno longer takes(public_key, ca_cert, ca_key)— instead it takes(public_key, &Issuer). The newCertifiedIssuer::self_signed(params, key)constructor returns a value that holds both the self-signed cert (for the trust store) and the signing identity (via Deref-to-Issuer for issuing leaves), so it's a clean drop-in for the "CA that needs to both sign leaves and be added to a root store" pattern inpeer_certs_reach_handler.The
CertifiedKey::key_pairfield was also renamed tosigning_key(used in tests/streaming).Security-advisory pins
Pinned to the patched floor while keeping the original major caret semantics:
tracing-subscriberregex0.3.20is still a caret pin (>=0.3.20, <0.4.0); same shape as before, just with a higher floor. Same for1.5.5. Touched in conformance, eliza, and multiservice fortracing-subscriber; eliza only forregex.Held back
criterionstays at 0.5 —pprof 0.15still pinscriterion ^0.5for itsPProfProfilerbench integration. Bumping criterion past 0.5 would mean giving up the bench-time profiler hook. Worth revisiting once pprof loosens that constraint.Transitive updates (selected)
cargo updatepicked up many compatible bumps:tokio1.49 → 1.50,hyper1.8 → 1.9,zerocopy0.8.40 → 0.8.48,tempfile3.26 → 3.27, plus the usual icu/wasm-bindgen/symbolic refreshes.Cargo.lockis gitignored (library workspace) so the lockfile diff isn't in this PR, but these will all be picked up on the nextcargo buildagainst the newCargo.tomlconstraints.Test Plan
task fmt,task clippy --workspace --all-features -- -D warnings,task test --workspace --all-features— all clean.