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

zero-release review

Free#24 of 29 in Release Automation Tools

A free Bash release tool that calculates SemVer from Conventional Commits and runs in GitHub Actions.

6.3/10Editor score
zero-release6.3 Visit zero-release

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

For repositories that use Conventional Commits, zero-release automates version decisions and release steps through a Bash CLI or composite GitHub Action. It analyzes commits to determine whether the next release is major, minor, patch, or no release, then calculates the SemVer version, creates Git tags, and generates release notes. Its free, open-source model and Linux platform scope make it a fit for solo developers and small or mid-market teams already working with GitHub Actions. It is less suited to teams that need a verified non-Linux platform or a release workflow centered on another source platform.

The core release process can be extended with optional plugins rather than requiring every repository to use the same steps. Plugins can update a changelog or package.json, publish to npm or GitHub Releases, and send notifications through Slack, Google Chat, or generic webhooks. This modularity is useful when a team wants to add only the parts its repository needs; those publishing and notification functions depend on their respective plugins. Dry-run previews, including default dry-run behavior on pull requests, provide a way to inspect a release before it proceeds.

The tool can run locally or as a GitHub Action, and its core requires no Node, jq, Python, or gh runtime dependencies. Configuration is supplied through CLI flags, action inputs, and environment variables instead of a releaserc file, so teams expecting that configuration-file approach may prefer another tool. Documentation and community support are the listed support channels. Choose zero-release if a Linux-based GitHub workflow needs a Bash-centered, modular path from Conventional Commits to tagged releases; look elsewhere if the workflow must run on another verified platform or requires all release steps built into the core.

zero-release pros and cons

  • Where it wins
    • Calculates SemVer and creates Git tags from Conventional Commits
    • Dry-run previews help check releases before publishing
    • Optional plugins cover changelogs, publishing, and notifications
  • Where it doesn't
    • Verified platform scope is Linux
    • Publishing and notification steps require optional plugins
    • Configuration uses flags, action inputs, and environment variables

zero-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