repver v0.6.0 was released on March 14, 2026, bringing a fresh visual upgrade to your version automation workflow. This release focuses on improving how you see repver’s output—making it easier than ever to scan results and understand what’s happening at a glance.

If you use repver to batch-update version strings across your Git repositories, this enhancement makes the experience more polished without changing how anything works under the hood.

What’s new

Colorized terminal output

The headline feature in v0.6.0 is colorized terminal output. repver now uses colors to help you distinguish different types of information:

  • Errors appear in bold red
  • Added lines (in diffs) show in green
  • Removed lines (in diffs) show in red
  • Dry-run messages highlight in yellow
  • Help text and info display in cyan

This visual separation helps you quickly identify what matters when repver runs, especially in longer outputs or when scanning logs.

Disable colors when you need to

Not every terminal environment plays nicely with color codes. v0.6.0 gives you full control:

# Use the --no-color flag
repver --command=goversion --param-version=1.26.0 --no-color

# Or set the NO_COLOR environment variable (follows no-color.org standard)
NO_COLOR=1 repver --command=goversion --param-version=1.26.0

The NO_COLOR environment variable follows the industry-standard convention, so it works consistently with your other CLI tools.

Improved dry-run mode

Dry-run mode now uses colors to make preview output stand out. When you run repver in dry-run mode, all [DRYRUN] messages appear in yellow, making it easy to see what would happen without executing any changes.

Smarter no-op behavior

When repver detects that your target files already contain the requested values, it now exits cleanly without touching your repository at all—no branch created, no commits made. This means less noise when running repver on unchanged code.

Why it matters

This release is about refining the user experience without disrupting your workflow. The colorized output is purely cosmetic—it doesn’t change how repver operates or what it produces. Your existing .repver configuration files work exactly as before, and all previous commands continue to function identically.

The improvements in v0.6.0 make repver more pleasant to use day-to-day while maintaining complete backward compatibility with v0.5.0. Whether you’re doing a quick version bump or orchestrating complex batch updates across multiple files, the tool behaves the same—it just looks better while doing it.

Upgrade today

Upgrading to v0.6.0 is straightforward since there are no breaking changes:

Download the binary for your platform from the GitHub Release page:

  • macOS (Intel): repver-v0.6.0-darwin-amd64.tar.gz
  • macOS (Apple Silicon): repver-v0.6.0-darwin-arm64.tar.gz
  • Linux (x86_64): repver-v0.6.0-linux-amd64.tar.gz
  • Linux (ARM64): repver-v0.6.0-linux-arm64.tar.gz
  • Windows (x86_64): repver-v0.6.0-windows-amd64.zip

Install from source

If you prefer building from source with Go 1.26.1 or later:

go install github.com/UnitVectorY-Labs/repver@v0.6.0

This post was AI-generated using the unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M model. Release information sourced from the repver repository, release v0.6.0 published on March 14, 2026. Author: release-storyteller