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

Versionary review

Free#8 of 29 in Release Automation Tools

A self-hosted release planner for GitHub projects, including multi-ecosystem monorepos.

7.9/10Editor score
Versionary7.9 Visit Versionary

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Versionary automates release planning for software maintainers who use Conventional Commits and GitHub. It computes semantic version increments, generates changelog entries, updates configured version files, and creates release tags and GitHub release metadata. Its ecosystem strategies cover Node, Rust, Python, R, Julia, LaTeX, and plain text. Independent or fixed versioning makes it relevant to projects coordinating multiple packages in a monorepo, while solo maintainers and small or mid-market teams are also listed as fits.

Release workflow is a central choice: Versionary can create a release directly or prepare a reviewable release pull request. CLI commands cover verification, release planning, changelog preview, and release execution. GitHub and GitHub Actions are the listed integrations, and deployment is self-hosted across Linux, macOS, and Windows, with an API platform also listed. This fits teams that want release decisions and version updates in their GitHub workflow; projects relying on another source host may find the fit narrower.

The project is MIT-licensed open-source software, so its free status refers to the software rather than a hosted service. A key boundary is package publishing: Versionary creates tags and release metadata but does not publish artifacts to language registries, leaving that work to CI tooling. Its documentation identifies the project as early alpha-stage, an important consideration for teams weighing maturity. Choose it if Conventional Commit-based planning, reviewable release changes, and monorepo versioning address your release process. Consider an alternative if registry publishing must be built in or you need a project beyond early alpha-stage.

Versionary pros and cons

  • Where it wins
    • Plans semantic versions and changelogs from Conventional Commits
    • Supports independent or fixed monorepo versioning
    • Offers direct releases or reviewable release pull requests
  • Where it doesn't
    • Does not publish packages to language registries
    • GitHub is the verified source-host integration
    • Documentation identifies the project as early alpha-stage

Versionary 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