Repository navigation
chore: release v0.3.0, add LICENSE + git_only fix for release-plz - #9
Merged
Merged
Conversation
Three bundled changes that together get this repo into a healthy post-v0.2.0 state: - Cargo.toml: bump 0.2.0 -> 0.3.0 for the pending process_info + process_tree work. CHANGELOG.md gets the [0.3.0] entry. - release-plz.toml: add git_only = true. Without it, publish=false still leaves release-plz querying crates.io to determine the latest version. Since the crate was never published, the query returns "not found," release-plz treats current Cargo.toml as the latest tagged release, and feat: commits since the actual git tag never trigger a bump. git_only=true uses git tags as the baseline instead. This is the actual root cause of why we needed manual bumps for v0.2.0 and would have needed one for v0.3.0. - LICENSE + Cargo.toml license field: MIT, matching cgroup-mcp. Same git_only fix is going up on cgroup-mcp in parallel (preventive since it hasn't tripped the bug there yet). Co-Authored-By: Claude Opus 4.7 (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
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.
Summary
Three bundled changes to get the repo into a healthy post-v0.2.0 state:
Why git_only
Per the release-plz docs (https://release-plz.dev/docs/config), `publish = false` only skips `cargo publish`. release-plz still queries crates.io to determine the latest version. For a crate that was never published, the query returns "not found," release-plz falls back to treating current Cargo.toml as the latest tagged release, and feat: commits since the actual git tag never trigger a bump.
`git_only = true` makes release-plz use git tags as the version baseline. Correct model for repos distributing only via GitHub Releases.
The same fix is going up on cgroup-mcp in parallel (preventive — that repo hasn't tripped the bug because only chore/ci commits have landed since v0.1.0).
Expected flow after merge
Test plan
🤖 Generated with Claude Code