The workspace uses bincode 1.3.3 (dora-message wire codec: daemon↔node TCP, inter-daemon events, recordings) and bincode 2.0.1 (coordinator-store persisted values). Both are flagged unmaintained (RUSTSEC-2025-0141, waived in deny.toml), and upstream's "latest" release cannot be adopted:
Migration options to evaluate post-1.0:
- bincode 2's serde compat layer with
config::legacy(), which is documented to be byte-compatible with bincode 1's default format — would unify on 2.0.1 without a wire break (verify with golden-bytes tests before switching).
- A maintained alternative (e.g. postcard), which is a wire break and needs a protocol-version bump — could be batched with the uhlc 0.9 migration (see the uhlc issue) so we pay for one coordinated break, not two.
Deferred from the dependency-upgrade PR #2445.
🤖 Generated with Claude Code
The workspace uses bincode 1.3.3 (dora-message wire codec: daemon↔node TCP, inter-daemon events, recordings) and bincode 2.0.1 (coordinator-store persisted values). Both are flagged unmaintained (RUSTSEC-2025-0141, waived in
deny.toml), and upstream's "latest" release cannot be adopted:compile_error!("https://xkcd.com/2347/"). Development moved to sourcehut (https://sr.ht/~stygianentity/bincode/).Migration options to evaluate post-1.0:
config::legacy(), which is documented to be byte-compatible with bincode 1's default format — would unify on 2.0.1 without a wire break (verify with golden-bytes tests before switching).Deferred from the dependency-upgrade PR #2445.
🤖 Generated with Claude Code