chore: release 0.3.0 - #55
Merged
Merged
Conversation
Headline change since 0.2.0: declarative input→test rules via `[workspace.metadata.affected]`. They close the blind spot where a test reads a non-Rust input at runtime (an insta `.snap`, a doc `.md`, an `include_str!` target) that has no coverage row, so a change to it selected no test. A rule pairs input globs with a nextest filterset; `[*.metadata]` is excluded from the manifest fingerprint, so editing a rule is cache-neutral. Pushing the `v0.3.0` tag after this merges triggers the crates.io publish workflow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cargo-affected-bot
approved these changes
Jun 15, 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.
Release 0.3.0.
Headline change since 0.2.0: declarative input→test rules via
[workspace.metadata.affected](#53). They close the blind spot where a test reads a non-Rust input at runtime (an insta.snap, a doc.md, aninclude_str!target) that has no coverage row, so a change to it selected no test. A rule pairs input globs with a nextest filterset, and[*.metadata]is excluded from the manifest fingerprint so editing a rule is cache-neutral.This bumps the crate version in
Cargo.tomlandCargo.lock; no code changes. Pushing thev0.3.0tag after this merges triggers the crates.io publish workflow (release.yaml).