Skip to content

ci: setup release-please - #162

Merged
roxblnfk merged 1 commit into
installerfrom
ci/release-please
Oct 27, 2026
Merged

roxblnfk merged 1 commit into
installerfrom
ci/release-please

Conversation

@roxblnfk

Copy link
Copy Markdown
Member

What was changed

  • release-please runs on pushes to installer and keeps a release PR with the next version and CHANGELOG.md built from conventional commits; merging it tags the release (3.x.y, no v prefix).
  • The first release PR collects everything since 3.9.0.
  • The installer deletes CHANGELOG.md from generated projects, as it does with LICENSE and .github.

Why?

To release from conventional commits instead of tagging by hand.

Checklist

  • Tested
    • Installer feature test (Console) passes with the changelog removal
    • Unit tests added

Review notes

  • The PR title becomes the squash commit (COMMIT_OR_PR_TITLE), so it must be conventional; the lines of a multi-change commit body are parsed as separate changes.
  • A feat!: or BREAKING CHANGE bumps the major version: feat!: move to RoadRunner 3 and roadrunner-bridge 5, add llm/skills #160 is titled feat!: and would release 4.0.0. Rename it to feat: to stay on 3.x.

chore: remove CHANGELOG.md from generated projects

Releases are tagged from the `installer` branch, so release-please targets it; `bootstrap-sha` is the 3.9.0 commit. The changelog lives in the project root that `composer create-project` copies, so the installer deletes it like LICENSE.

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
@roxblnfk
roxblnfk merged commit f75cbae into installer Oct 27, 2026
8 checks passed
@roxblnfk
roxblnfk deleted the ci/release-please branch October 27, 2026 18:47
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