Skip to main content
zerv versions every build relative to the latest tag reachable from HEAD. A repository — or branch — with no tags has no base version, so zerv stops instead of inventing 0.0.0.

​
Reproduce

Any commit in a repo that has no tags yet:

​
Fix

  • Create the first tag: git tag v0.1.0 && git push origin v0.1.0
  • Seed the base version explicitly when tagging is not yours to do: zerv flow --tag-version "v0.1.0"
  • In CI, check out with full history: a shallow clone (fetch-depth: 1) can cut the tags off. zerv’s reusable workflow uses fetch-depth: 0 for exactly this reason.
See the version CLI for every override that can stand in for VCS-detected values. Not this error? Every fix lives on zerv errors and troubleshooting.
Last modified on August 25, 2026