Skip to content

chore: release main#596

Open
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main
Open

chore: release main#596
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 18, 2026

🤖 I have created a release beep boop

cli: 3.0.0

3.0.0 (2026-04-19)

⚠ BREAKING CHANGES

  • cli: rename all skills and agents to consistent ce- prefix (#503)

Features

  • ce-review: add per-finding judgment loop to Interactive mode (#590) (27cbaf8)

Code Refactoring

  • cli: rename all skills and agents to consistent ce- prefix (#503) (5c0ec91)
compound-engineering: 3.0.0

3.0.0 (2026-04-19)

⚠ BREAKING CHANGES

  • cli: rename all skills and agents to consistent ce- prefix (#503)

Features

  • ce-review: add per-finding judgment loop to Interactive mode (#590) (27cbaf8)

Bug Fixes

  • ce-plan: close exit gates and honor user-named resources (#597) (d8e87c1)
  • ce-plan: run ambiguity gate before the non-software catch-all (#598) (49249d7)
  • ce-work: reject plan re-scoping into human-time phases (#600) (b575e49)

Code Refactoring

  • cli: rename all skills and agents to consistent ce- prefix (#503) (5c0ec91)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot added the autorelease: pending Release PR pending merge label Apr 18, 2026
@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from 2e4c88d to f274a5c Compare April 18, 2026 22:44
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
@github-actions github-actions bot force-pushed the release-please--branches--main branch from f274a5c to 235bc3c Compare April 19, 2026 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: pending Release PR pending merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants