Skip to content

Release 0.9.0: the verdict reads the boot output, not just the environment #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Zenofex merged 1 commit into from
Sep 28, 2026
+12 −5
Merged

Release 0.9.0: the verdict reads the boot output, not just the environment #22

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,12 @@ All notable changes to bootintel-cli are documented here. Format follows [Keep a

## [Unreleased]

## [0.9.0] — 2026-09-28 — the verdict reads the boot output, not just the environment

Both halves of the boot-chain verdict now agree about the same device: the engine and
the CLI reproduce one committed expectation byte for byte, across five fixtures, two
of them real captures rather than synthetic.

### Added
- **`bootintel verdict` now reports what the bootloader actually verified**, not
only what the environment says it is configured to do. A capture containing
Expand Down Expand Up @@ -678,7 +684,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.8.0...HEAD
[Unreleased]: https://github.com/bootintel/cli/compare/cli-v0.9.0...HEAD
[0.9.0]: https://github.com/bootintel/cli/releases/tag/cli-v0.9.0
[0.8.0]: https://github.com/bootintel/cli/releases/tag/cli-v0.8.0
[0.7.0]: https://github.com/bootintel/cli/releases/tag/cli-v0.7.0
[0.6.1]: https://github.com/bootintel/cli/releases/tag/cli-v0.6.1
Expand Down
4 changes: 2 additions & 2 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ members = ["crates/detectors", "crates/cli"]
resolver = "2"

[workspace.package]
version = "0.8.0"
version = "0.9.0"
edition = "2021"
rust-version = "1.90"
license = "Apache-2.0"
Expand Down
2 changes: 1 addition & 1 deletion crates/cli/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.8.0" }
bootintel-detectors = { path = "../detectors", version = "0.9.0" }
clap = { version = "4.5", features = ["derive", "wrap_help", "env"] }
# Shell-completion emitters for `bootintel completions <shell>`. Version
# tracks the clap major/minor (4.5). No default features — we only use
Expand Down
Loading