Merged
Conversation
PR #583 squash-merged with an empty body, which dropped the `Release-As:` footers that were supposed to neutralize the breaking marker on #578. Release-please still sees `chore(claude-permissions-optimizer)!: remove skill` in the commit range and keeps computing a 3.0.0 bump. This empty commit reintroduces the footers so the linked `cli` / `compound-engineering` group resolves to 2.67.0. The BREAKING CHANGES section may still render in the generated changelog because the `!` commit remains in history — hand-edit the release PR body before merge if so. Release-As: cli@2.67.0 Release-As: compound-engineering@2.67.0
tmchow
added a commit
that referenced
this pull request
Apr 18, 2026
…e- prefix (#503)" This reverts commit 5c0ec91. The rename landed before the work was ready. Reverting so it can be continued on the original feature branch and reopened as a new PR. The `!` marker on #503 caused release-please PR #596 to propose 3.0.0. The `Release-As:` footers below pin the linked cli/compound-engineering bump back to 2.69.0 (reflecting the remaining feat+fixes in that release window), mirroring the precedent set by #583/#585. Release-As: cli@2.69.0 Release-As: compound-engineering@2.69.0
4 tasks
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
3.0.0forcliandcompound-engineeringeven after chore: undo accidental breaking marker on #578 #583 landed, because chore: undo accidental breaking marker on #578 #583 was squash-merged with an empty body and theRelease-As:footers were dropped.1995e3d7 chore(claude-permissions-optimizer)!: remove skillis still in the commit range, so release-please still computes a major bump and nothing onmaincurrently overrides it.Release-As:footers so the linkedcli/compound-engineeringgroup pins back to2.67.0.Behavior
chore: pin next release to 2.67.0with:Release-As: cli@2.67.0Release-As: compound-engineering@2.67.02.67.0for both packages.BREAKING CHANGESsection may still appear in the regenerated changelog because the original!commit remains in history. Hand-edit the release PR body before merging if so.Test plan
2.67.0(not3.0.0) forcliandcompound-engineering.BREAKING CHANGESsection from the release PR body if release-please still includes it.