Skip to content

chore: undo accidental breaking marker on #578#583

Merged
tmchow merged 2 commits intomainfrom
tmchow/undo-major-bump
Apr 17, 2026
Merged

chore: undo accidental breaking marker on #578#583
tmchow merged 2 commits intomainfrom
tmchow/undo-major-bump

Conversation

@tmchow
Copy link
Copy Markdown
Collaborator

@tmchow tmchow commented Apr 17, 2026

Summary

  • PR chore(claude-permissions-optimizer)!: remove skill #578 (chore(claude-permissions-optimizer)!: remove skill) was merged with a ! in the subject, which release-please interpreted as a breaking change and used to force a 3.0.0 major bump in the pending release PR (chore: release main #576).
  • The change itself is a routine deprecation -- the claude-permissions-optimizer skill was superseded by Anthropic's first-party /less-permission-prompts -- and shouldn't gate users behind a major version.
  • This PR neutralizes the marker by reverting chore(claude-permissions-optimizer)!: remove skill #578 and immediately re-applying the same diff under a non-breaking commit message, plus a Release-As: cli@2.67.0 / Release-As: compound-engineering@2.67.0 footer to pin the linked-versions bump back to a minor release.

Behavior

  • Net diff against main is zero -- the skill stays removed.
  • Two commits land:
    • revert: chore(claude-permissions-optimizer): remove skill
    • chore(claude-permissions-optimizer): drop skill in favor of /less-permission-prompts (with Release-As: footers)
  • Once merged, release-please should regenerate PR chore: release main #576 as 2.67.0 for both cli and compound-engineering. The "BREAKING CHANGES" section may still appear in the regenerated changelog because the original ! commit remains in history; if so, hand-edit the release PR body before merging.

Test plan

  • Confirm CI is green on this PR.
  • After merge, verify release PR chore: release main #576 regenerates with version 2.67.0 (not 3.0.0) for cli and compound-engineering.
  • Hand-edit the release PR body to drop the "BREAKING CHANGES" section if release-please still includes it.

tmchow added 2 commits April 16, 2026 22:39
Reverts #1995e3d7 to neutralize the breaking-change marker that
incorrectly forced a major version bump. The change is re-applied in
the next commit with a non-breaking commit message.
…mission-prompts

Re-application of #578 with a non-breaking commit message. The
original commit was inadvertently marked with `!`, which forced a
3.0.0 major version bump despite this being a routine deprecation in
favor of the first-party Anthropic skill that supersedes it.

Release-As: cli@2.67.0
Release-As: compound-engineering@2.67.0
@tmchow tmchow merged commit 729fa19 into main Apr 17, 2026
2 checks passed
tmchow added a commit that referenced this pull request Apr 17, 2026
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
This was referenced Apr 17, 2026
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant