deps: bump the dependencies group across 1 directory with 9 updates

Cargo.toml

@@ -33,8 +33,8 @@ all = { level = "warn", priority = -1 }
 # found for type `str`). These versions work on Rust 1.85.
 # Remove these constraints once yoke-derive 0.8.4+ fixes the issue.
 [workspace.dependencies]
-yoke = "=0.8.2"
-yoke-derive = "=0.8.2"
-zerotrie = "=0.2.4"
-zerovec = "=0.11.6"
-potential_utf = "=0.1.5"
+yoke = "=0.8.3"
+yoke-derive = "=0.8.4"
+zerotrie = "=0.2.5"
+zerovec = "=0.11.8"
+potential_utf = "=0.1.6"

crates/bitty-network-tls/Cargo.toml

@@ -19,7 +19,7 @@ bitty-network-api = { path = "../bitty-network-api", version = "0.0.1" }
 # native roots, PKI types for certificates/keys/PEM, IDNA for canonical-host
 # normalization, and zeroize for key buffers. Exact pins match bitty-network.
 rustls = { version = "=0.23.45", default-features = false, features = ["std", "aws-lc-rs"] }
-rustls-platform-verifier = { version = "=0.7.0", default-features = false }
+rustls-platform-verifier = { version = "=0.7.1", default-features = false }
 rustls-pki-types = { version = "=1.15.1", default-features = false, features = ["std"] }
 idna = { version = "=1.1.0" }
 zeroize = { version = "=1.9.0", features = ["alloc"] }
@@ -38,6 +38,8 @@ potential_utf = { workspace = true }
 # runtime and keep them outside the repository, so no certificate or key
 # fixture is ever committed. `default-features = false` with `aws_lc_rs`
 # avoids pulling a second crypto provider into the test build.
+# Pinned to 0.13.x: rcgen 0.14+ requires rustc 1.88 and reworks the signing API
+# around Issuer, above this repo's MSRV 1.85. Revisit on MSRV rise.
 rcgen = { version = "=0.13.2", default-features = false, features = ["aws_lc_rs", "pem"] }
 # `OffsetDateTime` is the type of a generated certificate's validity window.
 # Already in the graph through rcgen; a dev-dependency so the test-only

crates/bitty-network/Cargo.toml

@@ -49,6 +49,8 @@ rustls = { version = "=0.23.45", default-features = false, features = ["std"], o
 # and private key at runtime and keep them outside the repository, so no
 # certificate or key fixture is ever committed. `default-features = false`
 # with `aws_lc_rs` avoids pulling a second crypto provider into the test build.
+# Pinned to 0.13.x: rcgen 0.14+ requires rustc 1.88 and reworks the signing API
+# around Issuer, above this repo's MSRV 1.85. Revisit on MSRV rise.
 rcgen = { version = "=0.13.2", default-features = false, features = ["aws_lc_rs", "pem"] }
 rustls-pki-types = "1.15.1"
 # `OffsetDateTime` is the type of a generated certificate's validity window.

deny.toml

@@ -89,13 +89,18 @@ wildcards = "deny"
 # - r-efi 5.3.0 (via phodopus getrandom 0.3.x) alongside 6.0.0 (via reqwest getrandom 0.4.x).
 #   Phodopus pins rand 0.9.x ecosystem; websocket/http use rand 0.10.x ecosystem.
 #   Will unify when Phodopus updates or when published to crates.io.
+#
+# Duplicate versions from the icu patch updates (dependabot #84):
+# - synstructure 0.13.2 (via phodopus gc-arena-derive) alongside 0.14.0
+#   (via yoke-derive 0.8.4). Unifying is gc-arena upstream's release to make.
 skip = [
     { crate = "base64@0.22.1", reason = "reqwest-tree dupe, upstream unification pending" },
     { crate = "syn@2.0.119", reason = "reqwest-tree dupe, upstream unification pending" },
     { crate = "rand_core@0.9.5", reason = "phodopus git dep uses rand 0.9.x, will unify on phodopus publish" },
     { crate = "rand@0.9.5", reason = "phodopus git dep uses rand 0.9.x, will unify on phodopus publish" },
     { crate = "getrandom@0.3.4", reason = "phodopus git dep uses getrandom 0.3.x, will unify on phodopus publish" },
     { crate = "r-efi@5.3.0", reason = "phodopus git dep uses r-efi 5.x, will unify on phodopus publish" },
+    { crate = "synstructure@0.13.2", reason = "phodopus gc-arena pins 0.13.x, yoke-derive 0.8.4 uses 0.14.x; unify on gc-arena release" },
 ]
 
 [sources]