Milestones
List view
Stability candidate. 0.11 publishes the compatibility contract and installs enforcement that actually enforces — cargo-semver-checks with a forced release type on every pull request, per feature configuration, plus isolated feature tests, MSRV over every feature, a CLI install smoke test and a saved-screen format corpus — and makes the one remaining breaking change, the `Screen::unsupported()` view. Everything else is additive. After 0.11.0 there is no breaking change to a promised item before 1.0. 1.0 follows the readiness criteria in the tracking issue, not a date. The due date is a target, not a promise.
Due by September 20, 2026•1/17 issues closedWhat a failure still cannot show you, and what a test still cannot say. Every item here is measured against the 0.9.0 release. Two threads. First, the snapshot workflow made native: a readable `Screen::diff` for every failure outside insta, grid-aware redaction that keeps columns aligned, a `serde` feature for JSON, ANSI/SVG/HTML renderings and a CI report action built on them, `assert_screen_snapshot!` earning its name, a `regex` feature for expect-style users, a ratatui fixture with a fidelity test, and a Rust fixture binary so the suite stops depending on `/bin/sh`. Second, the design questions that stay open until a document with measurements settles them: Windows (#149), the emulator backend (#150), styled history (#146) and history addressing (#147) — each a decision to write down, not a patch to land.
No due date•35/35 issues closed