chore: release v0.3.2 - #201
Merged
Merged
Conversation
Contributor
soothfast gate |
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.
What changed
## Unreleasedheading inCHANGELOG.mdto## 0.3.2 - 2026-09-11and wrote its Overview and Upgrade notes.[workspace.package] versionand the eight[workspace.dependencies]requirements from0.3.1to0.3.2.Cargo.lock. Only version lines moved; no dependency was added, removed, or changed.README.mdandsoothfast.toml.Why
0.3.1 gave the action its
featuresand regeneration inputs, so CI could betold once what a repository needs. A developer running the CLI by hand still
repeated the same flags on every invocation, and two defects surfaced once
adopters started bumping across versions. This release carries all three
fixes:
soothfast.tomlholds the feature and package defaults, the gate stopsletting a reference it could not pin decide a verdict quietly, and the
changelog drops the bot's own regeneration commits instead of listing the
paperwork as changes.
Everything here is additive and opt-in. A repository on
soothfast = "0.3"picks it up without touching its manifest.
How was this tested
cargo fmt --all -- --check: clean.cargo clippy --workspace --all-targets -- -D warnings: clean.cargo test --workspace --no-fail-fast: 817 passed, 4 ignored, 1 failed. The failure isinvoke::tests::a_plain_directory_in_the_repo_is_not_a_worktree_root, which asserts the workspace root is not a linked git worktree. It fails from any linked-worktree checkout and passes from a plain one, which is what CI uses. Confirmed by running the same built test binary from both.cargo check --workspaceafter the bump: clean, all ten crates resolve at0.3.2.git log v0.3.1..master: it lists feat: read gate and changelog features from soothfast.toml #195, fix: pin the gate harness across an incompatible requirement #196 and fix: drop the soothfast bot's own commits from the changelog #199, and none of the four soothfast-bot regeneration commits. Those exclusions are the filter from fix: drop the soothfast bot's own commits from the changelog #199 running against real history.make gate BASE=masterwas not run. This commit changes no measured code.Checklist
make checkpasses (fmt, clippy-D warnings,cargo test --workspace)make gate BASE=masterpasses, or any intentional cost change is explained above///doc commentsREADME.md,docs/,soothfast:bind/soothfast:claimmarkers) updated if behavior changed