Skip to content

v0.16.0

Latest

Choose a tag to compare

@joaquinbejar joaquinbejar released this 13 Nov 11:55
· 1 commit to main since this release
v0.16.0
3b8c776

[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.
    Notably async-nats 0.50 → 0.52 (its jetstream::Context is what
    NatsTradePublisher::new and NatsBookChangePublisher::new take, so users
    of the nats feature need async-nats 0.52 too), tokio 1.54, uuid
    1.29, either 1.19, proptest 1.12 (dev); every other entry is written as
    X.Y of its current release. No code change was needed. bincode stays 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.toml include already left them out).

  • tokio is now an optional dependency behind a tokio feature (#324).
    Only BookManagerTokio and the nats publishers use it; the core order
    book (matching, levels, snapshots) does not. The feature is in default,
    so existing builds are unchanged. Build with default-features = false to
    drop Tokio from the dependency graph; BookManagerTokio and its
    re-exports in prelude and the crate root are then unavailable. The nats
    feature enables tokio. A new CI job builds and lints the crate with
    --no-default-features and checks that cargo tree -e normal shows no
    Tokio.