open-standards/wai/byte-exact-conformance/Cargo.toml
Transaction Science 1e435c861a toolchain: Rust 1.98.0, and MSRV follows
Latest stable (1.98.0, released 2026-08-18). The pin lives in more places than
is obvious, and missing one means CI silently builds an older compiler than the
dev box:

  - rust-toolchain.toml at the repo root
  - eoc/eoc-rs/rust-toolchain.toml, a second toolchain file
  - five CI workflows that hardcode a version instead of deferring to the file
    (wai-conformance, wai-neural-e2e, wai-byte-equality,
    joule-code-conformance, jouleclaw-public-surface-documented)

standards-build.yml needed no change, because it reads the toolchain file
rather than pinning inline. That is the pattern the other five should adopt.

MSRV raised to 1.98 across 26 manifests, following the earlier decision to have
the declared floor track the pin rather than drift behind it. Note this is a
support-policy change, not a mechanical one: it narrows which compilers can
consume these standards as libraries.

The pin stays exact, never `stable` — a pin that drifts is not a pin.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-08-26 08:33:46 -04:00

19 lines
710 B
TOML

# Cross-architecture byte-equality conformance for WAI's integer-exact paths.
#
# Deliberately a SEPARATE tiny crate: it #[path]-includes the pure-integer
# sources from wai-rs (rans.rs, int_synth.rs — single source of truth, no copy)
# so it compiles with NO system codec libraries and NO ONNX runtime. That is
# what lets the CI matrix run it on every OS/arch in about a minute, proving
# the `replicate` determinism contract on real silicon rather than asserting it.
[package]
name = "wai-byte-exact-conformance"
version = "0.1.0"
edition = "2024"
rust-version = "1.98"
license = "Apache-2.0"
publish = false
[dependencies]
serde = { version = "1", features = ["derive"] }
serde_json = "1"
sha2 = "0.10"