Skip to content

build: release with release-please - #30

Merged
blaipr merged 1 commit into
mainfrom
build/release-please
Oct 29, 2026
Merged

blaipr merged 1 commit into
mainfrom
build/release-please

Conversation

@blaipr

@blaipr blaipr commented Oct 29, 2026

Copy link
Copy Markdown
Member

Problem

Releases are cut by hand: a release/x.y.z branch that bumps the version and moves the Unreleased CHANGELOG entries, a squash merge, then a tag pushed from a laptop. Every step is a chance to forget something (the lockfile, a link ref, tagging the squashed commit).

Change

release-please now cuts releases, as github-actions[bot] with GITHUB_TOKEN (no App, no PAT):

  • release-please-config.json and .release-please-manifest.json, seeded with the current version and today's release commit as bootstrap-sha. Tags keep the v prefix, the release title is the tag, release PRs are titled chore: release vX.Y.Z, and breaking changes stay MINOR while pre-1.0.
  • The CHANGELOG is written from the squashed PR titles: feat under Added, fix under Fixed, perf under Changed, revert under Reverted. refactor, docs, test, build, ci, chore and style are hidden and release nothing on their own.
  • .github/workflows/release.yml, on push to main: runs release-please, then dispatches CI on the release branch, because a push made with GITHUB_TOKEN starts no workflow and the release PR needs its required checks. CI gains a workflow_dispatch trigger for that.
  • The tag trigger and the release job leave CI. Where there is an image, publishing moves to a job of release.yml that runs when a release is created.
  • The hand-edited CHANGELOG guard (check-changelog.sh, the changelog-rewrite label triggers) and the empty Unreleased section go away.
  • docs/releasing.md, CONTRIBUTING, CLAUDE.md, the README docs table and the PR template describe the new process.

Compatibility

No change for users. Contributors: a PR's title is now its CHANGELOG line and decides the next version.

Requires "Allow GitHub Actions to create and approve pull requests" in the repository's Actions settings.

Every merge into main updates one release PR that bumps the version and writes the CHANGELOG from the squashed PR titles; merging it creates the tag, the GitHub Release and, where there is one, the image. Runs as github-actions[bot]; CI on the release PR is dispatched, since a GITHUB_TOKEN push starts no workflow.
@blaipr
blaipr merged commit e1f6f27 into main Oct 29, 2026
2 checks passed
@blaipr
blaipr deleted the build/release-please branch October 29, 2026 18:40
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