What problem does it solve?
Releasing software involves many manual, error-prone steps—updating CHANGELOG, bumping package versions, creating pull requests, tagging, and publishing releases—which can lead to inconsistent release notes, missed commits, or incorrect tags.
Core Features & Use Cases
- Changelog preparation & approval: Guides drafting the new release section from commits and requires explicit user approval before proceeding.
- Version bump and PR workflow: Instructs updating package.json, committing on develop, and opening a PR to main for CI and review.
- Tagging and GitHub release creation: Details tagging the merged commit on main and creating a GitHub release with concise release notes.
- Use Case: A maintainer preparing a patch, minor, or major release for Chorus who needs a repeatable, review-gated process to ensure accurate notes and correct semantic versioning.
Quick Start
Draft the new CHANGELOG section, confirm the proposed version, bump package.json on develop, push the changes, open a PR to main, merge after CI passes, and then create the GitHub release with the new tag.