From a363541014df34eb872cb42518c651af41afff36 Mon Sep 17 00:00:00 2001 From: BootIntel Agent Date: Tue, 29 Sep 2026 08:08:31 +0000 Subject: [PATCH] Release 0.12.0: the dashboard can take the prompt too Ships #30. `--interrupt-autoboot` works with `--tui`, where it was refused rather than silently ignored, leaving the dashboard as the one mode that could not take the prompt. The verdicts render at the top of the findings pane, above the detector findings, because they were read from the device at the prompt and that is better evidence than anything matched out of the scrollback. MINOR: new behaviour, no flag renamed, no exit code changed, no schema broken. That was the last item on the gap list carried through the last several releases. Everything else moved on the engine side, which needs no release: the boot chain is now persisted on the scan, rendered in the dashboard, carried into the PDF report and compared between scans. 390 tests with --features tui, 369 without, clippy clean under -D warnings in both, rustfmt clean, release binary reports 0.12.0. Both version bumps landed first try, fourth release running for docs/releasing.md step 1. Co-Authored-By: Claude Opus 5 (1M context) --- CHANGELOG.md | 5 ++++- Cargo.lock | 4 ++-- Cargo.toml | 2 +- crates/cli/Cargo.toml | 2 +- 4 files changed, 8 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4ec26bf..bd6e7a2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,8 @@ All notable changes to bootintel-cli are documented here. Format follows [Keep a ## [Unreleased] +## [0.12.0] — 2026-09-29 — the dashboard can take the prompt too + ### Added - **`--interrupt-autoboot` works with `--tui`.** It was refused there rather than silently ignored, which was the right call while it was unwired, but it left @@ -752,7 +754,8 @@ Initial release. All six subcommands live; five branch-based milestones (M1-M5) - PDF report download subcommand — server-side endpoint exists but no client-side wrapper yet. - Windows support — the Rust code compiles for Windows and the release workflow builds it, but install.sh doesn't handle Windows yet (`.ps1` installer is a follow-up). -[Unreleased]: https://github.com/bootintel/cli/compare/cli-v0.11.0...HEAD +[Unreleased]: https://github.com/bootintel/cli/compare/cli-v0.12.0...HEAD +[0.12.0]: https://github.com/bootintel/cli/releases/tag/cli-v0.12.0 [0.11.0]: https://github.com/bootintel/cli/releases/tag/cli-v0.11.0 [0.10.0]: https://github.com/bootintel/cli/releases/tag/cli-v0.10.0 [0.9.0]: https://github.com/bootintel/cli/releases/tag/cli-v0.9.0 diff --git a/Cargo.lock b/Cargo.lock index bcea041..dfd8215 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -131,7 +131,7 @@ checksum = "b588b76d00fde79687d7646a9b5bdf3cc0f655e0bbd080335a95d7e96f3587da" [[package]] name = "bootintel" -version = "0.11.0" +version = "0.12.0" dependencies = [ "anyhow", "arboard", @@ -154,7 +154,7 @@ dependencies = [ [[package]] name = "bootintel-detectors" -version = "0.11.0" +version = "0.12.0" dependencies = [ "regex", ] diff --git a/Cargo.toml b/Cargo.toml index 83c4132..77e87a2 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -19,7 +19,7 @@ members = ["crates/detectors", "crates/cli"] resolver = "2" [workspace.package] -version = "0.11.0" +version = "0.12.0" edition = "2021" rust-version = "1.90" license = "Apache-2.0" diff --git a/crates/cli/Cargo.toml b/crates/cli/Cargo.toml index 818e8ae..a482d10 100644 --- a/crates/cli/Cargo.toml +++ b/crates/cli/Cargo.toml @@ -24,7 +24,7 @@ path = "src/main.rs" # version when packaging for crates.io, which rejects a bare path dep. # This is what publish = false was working around; publishing # bootintel-detectors first makes the workaround unnecessary. -bootintel-detectors = { path = "../detectors", version = "0.11.0" } +bootintel-detectors = { path = "../detectors", version = "0.12.0" } clap = { version = "4.5", features = ["derive", "wrap_help", "env"] } # Shell-completion emitters for `bootintel completions `. Version # tracks the clap major/minor (4.5). No default features — we only use