Pin BCX toolchain to Rust 1.96.1

Author: eldryoth

CHANGELOG.md

@@ -15,6 +15,10 @@ All notable BCX changes will be documented here.
 - Move all current workspace packages to package version `0.5.0`.
 - Count crate README files as package content in the crate version matrix
   guard.
+- Update the preferred pinned Rust toolchain to `1.96.1` while retaining
+  compatibility checks from `1.90.0` through `1.96.1`.
+- Require future deferrals in roadmap, release notes, pentest responses, and
+  limitations to name the exact scheduled version or version range.
 
 ## 0.4.0 - 2026-06-20
 

README.md

@@ -80,7 +80,7 @@ Not implemented yet:
 | --- | --- |
 | License | `EUPL-1.2` |
 | MSRV | Rust `1.90.0` |
-| Preferred toolchain | Rust `1.96.0` |
+| Preferred toolchain | Rust `1.96.1` |
 | Default target | `no_std` |
 | Runtime dependencies | small, explicit, and audited |
 | Unsafe policy | `unsafe_code = "forbid"` |
@@ -109,7 +109,8 @@ Compatibility evidence:
 | `1.93.0` | `cargo check --workspace --all-features` |
 | `1.94.0` | `cargo check --workspace --all-features` |
 | `1.95.0` | `cargo check --workspace --all-features` |
-| `1.96.0` | current pinned toolchain |
+| `1.96.0` | `cargo check --workspace --all-features` |
+| `1.96.1` | current pinned toolchain |
 
 ## Install
 

docs/IMPLEMENTATION_PLAN.md

@@ -38,9 +38,9 @@ Integrations make those bindings usable in real stacks.
 ## Non-Negotiable Engineering Rules
 
 - Root published crate name is `bcx`.
-- Rust stable `1.96.0` is the preferred toolchain.
+- Rust stable `1.96.1` is the preferred toolchain.
 - MSRV is Rust `1.90.0`.
-- Compatibility from Rust `1.90.0` through `1.96.0` must remain explicit in
+- Compatibility from Rust `1.90.0` through `1.96.1` must remain explicit in
   the README evidence table.
 - Edition 2024 and workspace resolver `3`.
 - Core crates are `no_std` by default.

docs/VERSION_PLAN.md

@@ -45,6 +45,10 @@ Every release should prefer:
 - bounded parsing and graph traversal before federation,
 - explicit capability-aware APIs even when enforcement is still simple.
 
+No roadmap, release note, pentest response, or limitation may defer work with
+phrases such as "future work", "later", or "deferred" unless it names the exact
+version or version range where the work is scheduled.
+
 No production claim is allowed before `1.0.0`.
 
 ## Crate Package Versioning
@@ -330,7 +334,8 @@ Verification:
 
 Exit criteria:
 
-- one statement shape can later be encoded and bound to any profile.
+- one statement shape is ready for canonical encoding in `v0.14.0` and native
+  binding in `v0.9.0`.
 
 ### v0.8.0 - Attestation Envelope
 
@@ -400,7 +405,8 @@ Verification:
 
 Exit criteria:
 
-- one checkpoint can later have many settlement receipts.
+- one checkpoint is ready for settlement policy in `v0.20.0` and multiple
+  receipt models in `v0.56.0`.
 
 ## Phase 2: Canonical Codec And Test Vectors
 
@@ -639,7 +645,8 @@ Verification:
 
 Exit criteria:
 
-- provider crates can be added later without changing statement semantics.
+- provider crates scheduled from `v0.58.0` through `v0.62.0` can be added
+  without changing statement semantics.
 
 ### v0.22.0 - Statement Verification
 
@@ -1627,7 +1634,7 @@ Exit criteria:
 
 ### v0.91.0 - MSRV Matrix Evidence
 
-Goal: prove Rust `1.90.0` through `1.96.0` compatibility.
+Goal: prove Rust `1.90.0` through `1.96.1` compatibility.
 
 Deliverables:
 

docs/toolchain-policy.md

@@ -6,7 +6,7 @@ BCX uses stable Rust.
 
 Baseline:
 
-- Preferred Rust: `1.96.0`
+- Preferred Rust: `1.96.1`
 - MSRV: `1.90.0`
 - Edition: `2024`
 - Resolver: `3`
@@ -26,7 +26,8 @@ Compatibility target:
 | `1.93.0` | `cargo check --all-features` |
 | `1.94.0` | `cargo check --all-features` |
 | `1.95.0` | `cargo check --all-features` |
-| `1.96.0` | full release gate |
+| `1.96.0` | `cargo check --all-features` |
+| `1.96.1` | full release gate |
 
 Before changing Rust versions, dependency versions, CI actions, or security
 tools, re-check current upstream status and document the reason in release
@@ -36,4 +37,4 @@ Normal CI uses `scripts/checks.sh` and must not depend on crates.io or GitHub
 latest-version lookups beyond normal cargo dependency resolution. Before a tag,
 run the matching release gate, such as `scripts/release_0_1_gate.sh`; that gate
 checks latest pinned cargo tools and GitHub Actions pins before compatibility
-checks across Rust `1.90.0` through `1.96.0`.
+checks across Rust `1.90.0` through `1.96.1`.

release-notes/RELEASE_NOTES_0.5.0.md

@@ -30,6 +30,11 @@ multi-parent graphs, offline explanation, and graph-aware cycle prevention.
   README header updates made after `v0.4.0`.
 - Count crate README files as package content in the crate version matrix
   guard.
+- Update the preferred pinned Rust toolchain to `1.96.1`.
+- Expand release-gate compatibility checks to cover Rust `1.90.0` through
+  `1.96.1`.
+- Require every deferral in roadmap, release notes, pentest responses, and
+  limitations to name the exact scheduled version or version range.
 
 ## Known Limitations
 
@@ -38,5 +43,6 @@ multi-parent graphs, offline explanation, and graph-aware cycle prevention.
 - No full graph traversal crate yet.
 - `CausalCycleGuard` is a hook; BCX does not store or traverse a complete graph
   in this release.
-- Missing parents are represented, but recovery and WHY bundle behavior remain
-  future `bcx-explain` work.
+- Missing parents are represented; recovery and WHY bundle behavior are
+  scheduled for `v0.26.0` (`bcx-explain` skeleton) and `v0.27.0`
+  (explanation bundles).

rust-toolchain.toml

@@ -1,3 +1,3 @@
 [toolchain]
-channel = "1.96.0"
+channel = "1.96.1"
 components = ["clippy", "rustfmt"]

scripts/release_0_1_gate.sh

@@ -6,6 +6,6 @@ scripts/validate-latest-tools.sh
 scripts/release_crate.py --check
 scripts/validate-release-readiness.sh v0.1.0
 
-for toolchain in 1.90.0 1.91.0 1.92.0 1.93.0 1.94.0 1.95.0 1.96.0; do
+for toolchain in 1.90.0 1.91.0 1.92.0 1.93.0 1.94.0 1.95.0 1.96.0 1.96.1; do
     cargo "+$toolchain" check --workspace --all-features
 done

scripts/release_0_2_gate.sh

@@ -6,6 +6,6 @@ scripts/validate-latest-tools.sh
 scripts/release_crate.py --check
 scripts/validate-release-readiness.sh v0.2.0
 
-for toolchain in 1.90.0 1.91.0 1.92.0 1.93.0 1.94.0 1.95.0 1.96.0; do
+for toolchain in 1.90.0 1.91.0 1.92.0 1.93.0 1.94.0 1.95.0 1.96.0 1.96.1; do
     cargo "+$toolchain" check --workspace --all-features
 done

scripts/release_0_3_gate.sh

@@ -8,6 +8,6 @@ scripts/validate-latest-tools.sh
 scripts/release_crate.py --check --version "$version"
 scripts/validate-release-readiness.sh "v$version"
 
-for toolchain in 1.90.0 1.91.0 1.92.0 1.93.0 1.94.0 1.95.0 1.96.0; do
+for toolchain in 1.90.0 1.91.0 1.92.0 1.93.0 1.94.0 1.95.0 1.96.0 1.96.1; do
     cargo "+$toolchain" check --workspace --all-features
 done