Skip to content

chore: pin next release to 2.67.0#585

Merged
tmchow merged 1 commit intomainfrom
tmchow/release-please-major-bump
Apr 17, 2026
Merged

chore: pin next release to 2.67.0#585
tmchow merged 1 commit intomainfrom
tmchow/release-please-major-bump

Conversation

@tmchow
Copy link
Copy Markdown
Collaborator

@tmchow tmchow commented Apr 17, 2026

Summary

  • Release-please PR chore: release main #584 keeps regenerating as 3.0.0 for cli and compound-engineering even 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 the Release-As: footers were dropped.
  • The breaking commit 1995e3d7 chore(claude-permissions-optimizer)!: remove skill is still in the commit range, so release-please still computes a major bump and nothing on main currently overrides it.
  • This PR lands a single empty commit carrying the Release-As: footers so the linked cli / compound-engineering group pins back to 2.67.0.

Behavior

  • No code change. One empty commit: chore: pin next release to 2.67.0 with:
    • Release-As: cli@2.67.0
    • Release-As: compound-engineering@2.67.0
  • After merge, release-please should regenerate PR chore: release main #584 as 2.67.0 for both packages.
  • The BREAKING CHANGES section 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

  • CI green on this PR.
  • After merge, release PR chore: release main #584 regenerates with version 2.67.0 (not 3.0.0) for cli and compound-engineering.
  • Strip the BREAKING CHANGES section from the release PR body if release-please still includes it.

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 tmchow merged commit f6465c8 into main Apr 17, 2026
2 checks passed
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