Repository navigation
chore: release v0.2.0 - #5
Merged
Merged
Conversation
Manual unstick because release-plz's release-pr step did not propose a version bump after the two feat(tools) commits since v0.1.0, even after moving the v0.1.0 tag to the chore: release commit. Root cause is not fully understood; release-plz's release step short-circuits on "Cargo.toml=0.1.0 + tag v0.1.0 exists = already published" without running the conventional-commits scan. Bumping Cargo.toml manually gets release to tag v0.2.0 and publish binaries; future bumps from v0.2.0 onward will tell us whether the issue recurs. Adds pids_in_cgroup and top_processes to the changelog. 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.
Why
release-plz's release-pr step didn't propose a version bump after the two
feat(tools):commits since v0.1.0 (pids_in_cgroupandtop_processes), even after moving the v0.1.0 tag to point at the chore-release commit. The release step short-circuits on "Cargo.toml=0.1.0 + tag v0.1.0 exists = already published" without running the conventional-commits scan.Fix
Manual bump:
Cargo.toml: 0.1.0 → 0.2.0CHANGELOG.md: add [0.2.0] entry mirroring what release-plz would have generatedAfter merge, release-plz's release step sees
Cargo.toml=0.2.0,v0.2.0tag doesn't exist, and creates the tag + GitHub Release + triggers the binary workflow.Next step diagnostically
Future feat: commits should let release-plz bump from v0.2.0 normally. If it gets stuck again on v0.3.0, the issue is structural (not just first-release weirdness) and we'll need to investigate release-plz config or version.
🤖 Generated with Claude Code