On January 24, 2026, we released repver v0.3.0. This update focuses on empowering users who manage dozens or hundreds of repositories by introducing a way to programmatically discover supported versioning commands and a completely refreshed documentation suite.

What’s new

The headline feature of v0.3.0 is the introduction of Exists Mode via the --exists flag.

Previously, running repver with a command that didn’t exist in a repository’s configuration would simply fail. Now, you can use the --exists flag in conjunction with --command to check if a specific versioning command is defined and valid within a repository’s .repver file. If the command exists, repver returns a success exit code (0); otherwise, it returns a failure code (1).

Crucially, in Exists Mode, repver performs no file modifications and no Git operations. It is a read-only check designed specifically for the needs of automation.

Alongside this new feature, we’ve completely overhauled our documentation:

  • Enhanced README: Our homepage now focuses on the “why” of repver, featuring a new Mermaid workflow diagram to help you visualize the automation process.
  • New Examples Page: We’ve added docs/EXAMPLES.md, providing a library of common patterns for standard updates and command discovery scripting.
  • Updated Reference: The command reference now includes detailed guidance on using the new --exists flag.

Why it matters

For developers and platform engineers managing a large fleet of services, the --exists flag is a game-changer. It allows you to write a single CI/CD script that can iterate through multiple repositories and conditionally execute repver only in those that have explicitly defined a supported versioning command. This removes the need for brittle custom checks or managing separate lists of “supported” repositories.

The documentation refresh ensures that whether you are a first-time user or a power user integrating repver into a complex pipeline, you have the clear guidance and concrete examples needed to get up and running quickly.

Getting started with v0.3.0

Upgrading to v0.3.0 is seamless, as there are no breaking changes to existing configuration files. You can update your repver installation using your preferred method. Once updated, you can immediately begin leveraging Exists Mode in your scripts to make your versioning workflows more resilient and scalable.

This post was AI-generated using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL. Generated on April 13, 2026, based on the repver v0.3.0 release. Author: release-storyteller