Turn merged commits into your next tagged release

flopha reads your Git tags and commit messages, picks the next semantic version, and creates the tag, changelog, and GitHub Release. It runs from your terminal, any CI, or as a GitHub Action.

$ git log --oneline v1.2.3..
3f2c1a9 fix: handle empty input
a1b2c3d feat: add release notes export

$ flopha next-version --auto
v1.3.0

When it fits

flopha treats Git tags (or branch names) as the source of truth for versions. It is a good fit when:

• You want the next version decided by commit messages instead of by hand.
• You want the tag, changelog, and GitHub Release from one command or one workflow step.
• Your versions have a custom shape, like desktop@1.4.2 or release/1.4.2.
• You keep the version in Cargo.toml, package.json, or pyproject.toml and want it written there before tagging.

Where to go next

• Installation: install the binary.
• Quick Start: calculate and create your first version, then release with one command.
• Release Workflows: CI pipelines, version PRs, and custom bump rules.