Stop building release PRs by hand.
brel reads commits, updates release files, and opens the release PR in GitHub.
- Plan releases faster
- Keep review in GitHub
What to check
Check three things in the repo.
-
Commit rules
See how commit history turns into the next version bump.
-
`brel.toml`
See how version files, changelog updates, tags, and branch naming are configured.
-
`release-pr`
Try the command locally before you add the workflow to a real repository.
FAQ
Questions teams ask.
What does better-releases automate?
better-releases automates the release PR flow in GitHub. brel reads commits, picks the next version, updates release files, refreshes the changelog, and opens the release PR.
How does brel pick the next version?
brel reads commits since the latest stable tag and uses Conventional Commits to choose the next SemVer bump.
How does this help with release planning?
It handles the release PR work for you, so your team can focus on deciding when to ship instead of preparing release branches, version files, and changelogs by hand.
Do I need a release dashboard?
No. better-releases keeps the workflow in GitHub, where your team already reviews code and pull requests.
What happens when there is nothing to release?
If the commits since the last stable tag do not call for a release, brel exits without opening a release PR.