Release 0.12.0: the dashboard can take the prompt too - #31
Merged
Merged
Conversation
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) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump, lockfile, changelog. No code changes: everything here is on
mainand was reviewed in #30.What ships
--interrupt-autobootworks with--tui. It was refused there rather than silently ignored, which was right while it was unwired and left the dashboard as the one mode that could not take the prompt.Verdicts sit above the detector findings because they were read from the device at the prompt, which is better evidence than anything matched out of the scrollback.
Why MINOR
New behaviour. No flag renamed or removed, no exit-code policy change, no output-format schema broken.
Verification
cargo test --workspace --features tui: 390 passed, 0 failedcargo test --workspace: 369 passed, 0 failedclippy --workspace --all-targets --features tui -- -D warningsandfmt --all --check: cleancargo build --release --features tuithenbootintel --versionreportsbootintel 0.12.0Both version bumps landed first try, fourth release running for
docs/releasing.mdstep 1.This was the last item on the gap list carried through the previous few releases. Everything else from the last two days 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.
After merge: dispatch
cli-releasefor0.12.0withpublish_crates, verify the draft againstSHA256SUMS, publish and mark latest, then move the tap (step 7) and sync the in-repo reference copy.🤖 Generated with Claude Code