Repository navigation
chore: release 0.4.1 - #112
Merged
Merged
Conversation
Three fixes to `run` and to the output, with no new CLI surface, no report-JSON schema change, and no change to the grep-able `cargo-affected:` summary line — so a patch. Deleting a test no longer makes `run` exit 4 (#81). The deletion's diff hunk covers exactly the lines of the deleted test's own stored coverage range, so the test selects itself, and nextest is then handed a filterset matching nothing. `run` now restricts the filterset to tests still in the listing and exits 0 with a note when that leaves nothing; `status` predicts the same. A change committed since the last collect that nothing covers now reports as uncovered (#92). The empty-selection message keyed off the working tree while selection diffs against each reachable `collect_sha`, so the change read as "no uncommitted changes ... nothing to run" directly under the "N commit(s) since collect" notice. Count nouns in `collect` and `run` output agree with their numbers (#82): "1 binary" rather than "1 binaryy", "1 test to run" rather than "1 tests to run". Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
cargo-affected-bot
approved these changes
Sep 18, 2026
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
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.
Three fixes to
runand to the output, with no new CLI surface, no report-JSON schema change, and no change to the grep-ablecargo-affected:summary line — so a patch.Deleting a test no longer makes
runexit 4 (#81). The deletion's diff hunk covers exactly the lines of the deleted test's own stored coverage range, so the test selects itself, and nextest is then handed a filterset matching nothing.runnow restricts the filterset to tests still in the listing and exits 0 with a note when that leaves nothing;statuspredicts the same.A change committed since the last collect that nothing covers now reports as uncovered (#92). The empty-selection message keyed off the working tree while selection diffs against each reachable
collect_sha, so the change read as "no uncommitted changes ... nothing to run" directly under the "N commit(s) since collect" notice.Count nouns in
collectandrunoutput agree with their numbers (#82): "1 binary" rather than "1 binaryy", "1 test to run" rather than "1 tests to run".cargo test(117 unit + 44 functional),cargo clippy --all-targets, andcargo publish --dry-runare all green locally.