chore: release 0.7.0 - #15
Merged
Merged
Conversation
Five merged PRs sat on main under a 0.6.0 version string: #10, #11, #12, #13 and #14. The marketplace compares declared versions, so a string that does not move is a release nobody receives -- the same failure #11 was written to catch, one release later and from the other side. The gate holds the declared version to a released changelog section; it cannot hold main to declaring the work that landed on it. Three commands gained surface -- `wb surface`, `wb status --stats --global`, `wb task clean --merged/--older-than` -- so this is a minor bump. No breaking change: every existing group, action, flag and exit code behaves as it did in 0.6.0, and no `--json` payload lost or renamed a key.
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
1 participant
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.
Five merged PRs sat on
mainunder a 0.6.0 version string: #10, #11, #12, #13, #14. The marketplace compares declared versions, so a string that does not move is a release nobody receives — the same failure #11 was written to catch, one release later and from the other side. That gate holds the declared version to a released changelog section; it cannot holdmainto declaring the work that landed on it.Bumps
.claude-plugin/marketplace.json,.claude-plugin/plugin.jsonandlib/workbench/__init__.pyto 0.7.0, and writes the section the gate now requires.Minor bump: three commands gained surface —
wb surface,wb status --stats --global,wb task clean --merged/--older-than— plus the base-measurement fix inwb pr contextandwb status.No breaking change: every existing group, action, flag and exit code behaves as it did in 0.6.0, and no
--jsonpayload lost or renamed a key.surfaceis a new payload atschema1;status --stats --globaladds a key rather than moving one.672 tests pass locally.
🤖 Generated with Claude Code