Errors
Every error gets its own page with the exact message, the cause, and the fix:
Running zerv shows help and exits
Running bare zerv prints the full help and exits with code 2. zerv requires a
subcommand: version, flow, check, or render. For example:
PEP440 output looks different from SemVer output
Not an error. The same version renders differently per format, by design:
PEP440 has no dots in pre-release segments. zerv check --format pep440 accepts the SemVer
spelling and reports the normalization:
Docker rejects the + in the version
SemVer build metadata uses +, which docker tags forbid. Render the docker-safe form
instead, which swaps + for -:
Stdin piping produces nothing
Piping into zerv version requires the upstream command to emit --output-format zerv
(the RON payload), not a plain version string:
Last modified on August 25, 2026
