Repository navigation
[0.16.0] - 2026-11-13
A feature release: tokio becomes an optional dependency behind a tokio
feature, on by default (#324). Default builds are unchanged; a build with
default-features = false no longer has Tokio or BookManagerTokio, hence
the minor bump. Dependencies move to their latest stable releases. No
snapshot or wire format change.
Changed
-
Dependencies at their latest stable releases, declared as
X.Y.
Notablyasync-nats0.50 → 0.52 (itsjetstream::Contextis what
NatsTradePublisher::newandNatsBookChangePublisher::newtake, so users
of thenatsfeature needasync-nats0.52 too),tokio1.54,uuid
1.29,either1.19,proptest1.12 (dev); every other entry is written as
X.Yof its current release. No code change was needed.bincodestays at
2.0: the 3.0.0 release on crates.io is a placeholder that does not compile. -
.codex/and.agents/are no longer tracked and are listed in
.gitignore. They hold local tooling configuration, never shipped in the
published crate (Cargo.tomlincludealready left them out). -
tokiois now an optional dependency behind atokiofeature (#324).
OnlyBookManagerTokioand thenatspublishers use it; the core order
book (matching, levels, snapshots) does not. The feature is indefault,
so existing builds are unchanged. Build withdefault-features = falseto
drop Tokio from the dependency graph;BookManagerTokioand its
re-exports inpreludeand the crate root are then unavailable. Thenats
feature enablestokio. A new CI job builds and lints the crate with
--no-default-featuresand checks thatcargo tree -e normalshows no
Tokio.