Skip to content

chore: release main#661

Merged
tmchow merged 1 commit intomainfrom
release-please--branches--main
Apr 24, 2026
Merged

chore: release main#661
tmchow merged 1 commit intomainfrom
release-please--branches--main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Apr 23, 2026

🤖 I have created a release beep boop

cli: 3.0.2

3.0.2 (2026-04-24)

Features

  • ce-ideate: subject gate, surprise-me, and warrant contract (#671) (6514b1f)

Bug Fixes

  • ce-update: compare against main plugin.json, not release tags (#660) (351d12e)
compound-engineering: 3.0.2

3.0.2 (2026-04-24)

Features

  • ce-commit-push-pr: skip evidence prompt when judgment allows (#663) (75cf4d6)
  • ce-ideate: subject gate, surprise-me, and warrant contract (#671) (6514b1f)

Bug Fixes

  • ce-brainstorm: enforce Interaction Rules in universal flow (#669) (494313e)
  • ce-demo-reel: prevent secrets in recorded demos (#664) (9ddcd22)
  • ce-update: compare against main plugin.json, not release tags (#660) (351d12e)
  • skills: plan is a decision artifact; progress comes from git (#666) (c33bf70)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot added the autorelease: pending Release PR pending merge label Apr 23, 2026
@github-actions github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from d7dfb84 to 8c7bf9c Compare April 24, 2026 04:53
@tmchow tmchow mentioned this pull request Apr 24, 2026
3 tasks
tmchow added a commit that referenced this pull request Apr 24, 2026
PR #663 squash-merged as `feat(ce-commit-push-pr):` — adding two
short-circuits that skip a blocking prompt when the agent just authored
the change. The intent was a UX/flow fix, not a new capability, so the
correct conventional prefix is `fix:`. Since the prefix drove a minor
bump, the open release PR (#661) is pinning the linked `cli` /
`compound-engineering` group at 3.1.0.

This empty commit reclassifies the pending release to 3.0.2 via
`Release-As:` footers so the patch-level fixes in this window
(#660 ce-update, #664 ce-demo-reel, #663 ce-commit-push-pr) land as
3.0.2 instead of 3.1.0. The feat prefix remains in history and may
still render under a Features heading in the generated changelog —
hand-edit the release PR body before merge if so.

Release-As: cli@3.0.2
Release-As: compound-engineering@3.0.2
@github-actions github-actions Bot force-pushed the release-please--branches--main branch from 8c7bf9c to e37d76f Compare April 24, 2026 05:01
@github-actions github-actions Bot force-pushed the release-please--branches--main branch 3 times, most recently from 7939d77 to 2141ad3 Compare April 24, 2026 06:57
@github-actions github-actions Bot force-pushed the release-please--branches--main branch from 2141ad3 to 76b31a1 Compare April 24, 2026 09:05
@tmchow tmchow merged commit 6b5da46 into main Apr 24, 2026
@github-actions
Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@github-actions github-actions Bot added autorelease: tagged and removed autorelease: pending Release PR pending merge labels Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant