You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest published Kani release, 0.67.0, bundles a Rust 1.93-era compiler. It fails before harness compilation when a workspace package declares rust-version = "1.95":
error: rustc 1.93.0-nightly is not supported by packages requiring rustc 1.95
This makes pinned, released Kani unusable for current Rust 1.95 workspaces even when the proof harness itself is otherwise compatible.
Current upstream readiness
As of 2026-07-28, main pins nightly-2026-02-12; the official Rust manifest identifies that compiler as 0.96.0-nightly. PR #4683 is advancing it again to nightly-2026-02-14.
Request
Please publish a concrete Kani release with the newer bundled toolchain, or document the intended release path/timeline. A published version is needed so downstream verification can remain reproducibly pinned rather than relying on an unreleased main build or bypassing Cargo rust-version enforcement.
No compiler-version bypass, dependency downgrade, or unpinned proof result is being requested.
$ cargo kani
Kani Rust Verifier 0.67.0 (cargo plugin)
error: rustc 1.93.0-nightly is not supported by the following package:
kaniprobe@0.0.0 requires rustc 1.95
error: Failed to execute cargo (exit status: 101). Found 0 compilation errors.
Confirmed on the installed release: cargo-kani 0.67.0, whose bundled toolchain resolves to rustc 1.93.0-nightly (53732d5e0 2025-11-20).
"Found 0 compilation errors" is the salient part — the harness is never reached, so this is not a proof failure or an unsupported-feature issue. It is a manifest-level gate that fires before any codegen, on a crate whose only content is a trivially true assertion.
What it blocks
Two proof obligations in a security programme, on a workspace pinned to Rust 1.95.0. The three options available downstream are all bad:
wait for a release built on a newer toolchain (this issue);
downgrade the whole workspace two Rust versions to satisfy one prover;
verify under a separate 1.93 toolchain — which produces a proof about a different compilation than the one that ships, and a proof about code you don't ship is worth very little.
We have taken option 1 and recorded the obligations as blocked upstream rather than silently dropping them. No urgency implied — this is a heads-up that a published release, or a documented timeline, is what unblocks reproducibly-pinned downstream verification. Happy to test a release candidate against a real workspace if that would be useful.
Activity
kerberosmansour commentedon Aug 1, 2026
Adding a minimal reproduction and a note on what this blocks downstream, in case it helps triage.
Three-line repro
Confirmed on the installed release:
cargo-kani 0.67.0, whose bundled toolchain resolves torustc 1.93.0-nightly (53732d5e0 2025-11-20)."Found 0 compilation errors" is the salient part — the harness is never reached, so this is not a proof failure or an unsupported-feature issue. It is a manifest-level gate that fires before any codegen, on a crate whose only content is a trivially true assertion.
What it blocks
Two proof obligations in a security programme, on a workspace pinned to Rust 1.95.0. The three options available downstream are all bad:
We have taken option 1 and recorded the obligations as blocked upstream rather than silently dropping them. No urgency implied — this is a heads-up that a published release, or a documented timeline, is what unblocks reproducibly-pinned downstream verification. Happy to test a release candidate against a real workspace if that would be useful.
feliperodri commentedon Aug 1, 2026
We are planning to do a new release soon. We've been trying to bring the toolchain up to date.
feliperodri commentedon Aug 12, 2026
Released on: 16 April, 2026
feliperodri commentedon Sep 16, 2026
@kerberosmansour new release is out! https://github.com/model-checking/kani/releases/tag/kani-0.68.0
kerberosmansour commentedon Sep 16, 2026