Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

or-release review

Free#21 of 29 in Release Automation Tools

A free, convention-based CLI for version bumps and GitHub releases—not package publishing.

6.6/10Editor score
or-release6.6 Visit or-release

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

For small projects using GitHub, or-release is a free, open-source command-line tool that calculates semantic version bumps from commit conventions and changes since the previous version. It can publish a GitHub tag and associated release through the GitHub API, with a changelog-style list of changes in the release body. It runs on Linux, Windows, and macOS, and can be run locally or in a GitHub Actions workflow. Its focus is convention-based release creation rather than a broader release-management system.

The main fit question is how your project handles commits and release targets. or-release supports configurable commit conventions, including gitmoji, and accepts configuration through JSON, YAML, or TOML files, as well as environment variables and command-line options. A dry-run option lets maintainers check the prospective version without publishing. These features suit teams that want version calculation tied to their commit history and a predictable GitHub release step. Projects that do not follow a compatible convention may find this workflow less useful.

Its platform scope is deliberately narrow: GitHub is the supported release destination, while GitLab releases and direct git tagging are described as planned. Package publishing is not part of the listed capabilities, so teams seeking one tool to publish packages to registries should look elsewhere. Choose or-release when the need is calculating a version, creating GitHub tags and releases, and producing release-body changes; choose a broader release tool if your workflow depends on additional hosting platforms or package distribution.

or-release pros and cons

  • Where it wins
    • Calculates version bumps from commit conventions and changes since the prior version
    • Creates GitHub tags and releases, with a changelog-style release body
    • Dry runs and supports configurable conventions, including gitmoji
  • Where it doesn't
    • GitHub is the documented release platform; GitLab releases are planned
    • Does not list package publishing as a feature
    • Requires commit conventions to determine version bumps

or-release fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update