Git versioning CLI

Ship the next version without release-script sprawl

flopha finds the latest version, calculates the next semantic release, and creates it as a Git tag or branch from the same CLI flow.

Use it when releases still depend on shell glue, manual bump decisions, or repo rituals nobody wants to debug twice.

Typical release flow

Go from current version to next release in three commands

flopha last-version

See the current release before you decide what ships next.

flopha next-version --auto --pre rc

Generate the next release candidate from commit history instead of bumping by hand.

flopha next-version --source branch --create

Create the release branch directly when your version stream lives in branch names.

Resolve the next semantic version from Git history instead of manually checking tags, commit types, and pre-release counters.

Use Git tags by default, switch to release branches when needed, and keep custom version patterns without shell glue.

Generate alpha, beta, and rc versions from the next stable release so your team can ship previews without guesswork.

What it solves

Track versions like desktop@1.6.3 or release/1.6.3 without building repo-specific release scripts.

Promote `feat`, breaking changes, or your own message conventions into version math with `--auto` and `--rule`.

Generate `alpha`, `beta`, or `rc` series from the next stable version instead of keeping counters in your head.

Docs

Install the binary, add it to your PATH, and verify it inside a Git repository in a few minutes.

Start with the shortest path through last-version, next-version, auto bumping, and release creation.

See the full CLI surface when you want the exact flags for release creation, pre-releases, and history lookups.