8d2ff334d2
The repo was pinned to 1.96.0 while 1.97.1 is current and installed on the dev box, so every build here ran a compiler two releases behind the one the code is actually developed against. This moves the pin forward. Both toolchain files (root and the eoc/eoc-rs sub-workspace) and the five workflows that hardcode a toolchain rather than deferring to rust-toolchain.toml — wai-conformance, wai-neural-e2e, wai-byte-equality, joule-code-conformance, jouleclaw-public-surface-documented. Pinning stays exact, per the repo's convention: a pin that drifts is not a pin. MSRV is deliberately untouched. The `rust-version` fields across the workspaces (1.85 in mesh/proof, 1.96 elsewhere) declare the *oldest* compiler a crate supports, not the one it is built with — a floor, not a pin. Raising them because the dev toolchain moved would narrow who can consume these standards as libraries, which is a policy decision about support commitments, not a consequence of upgrading a build box. A crate with MSRV 1.85 builds perfectly well under 1.97.1. Co-Authored-By: Claude Opus 4.8 <[email protected]>
4 lines
122 B
TOML
4 lines
122 B
TOML
[toolchain]
|
|
channel = "1.97.1"
|
|
components = ["rustc", "cargo", "rust-std", "rustfmt", "clippy"]
|
|
profile = "default"
|