Introducing Scripting Support for Automated Workflows

We’re excited to announce the release of repver v0.3.0, a significant update that brings native scripting and CI/CD integration capabilities to this powerful version replacement tool. Released on January 24, 2026, this release bridges the gap between interactive use and automated workflows across multiple repositories.

For those unfamiliar, repver automates batch string replacements (like version numbers) across multiple files in Git repositories, handling the entire workflow from pattern matching to Git operations with a single command.

What’s New

The --exists Flag: Command Discovery for Scripts

The headline feature in v0.3.0 is the new --exists flag, designed specifically for scripting and CI/CD integration. This flag enables your automation scripts to detect whether a repository supports specific repver commands before attempting to execute them.

How it works:

  • Checks if a repository has a valid .repver configuration file
  • Verifies that the specified command is defined in the configuration
  • Returns exit code 0 if the command exists, non-zero otherwise
  • Performs no file modifications or Git operations (read-only check)

Practical example:

if repver --command=goversion --exists; then
  repver --command=goversion --param-version=1.25.6
else
  echo "Repository does not support goversion command"
fi

This capability transforms repver from an interactive tool into one that can seamlessly integrate into multi-repository automation pipelines, deployment scripts, and CI/CD workflows.

Documentation Enhancements

With the new --exists flag came comprehensive documentation updates:

  • Enhanced COMMAND.md with detailed flag documentation
  • New examples in EXAMPLES.md showing conditional execution patterns
  • README.md refinements for improved clarity

Why It Matters

The addition of scripting-friendly mode addresses a common challenge for teams managing multiple repositories. Previously, scripts needed to parse output or handle errors after the fact to determine if a repver command was applicable. The --exists flag provides a clean, exit-code-based approach that works naturally with shell conditionals and workflow orchestration tools.

For DevOps engineers and platform teams, this means:

  • Cleaner automation: No more fragile output parsing or error handling hacks
  • Safe conditional execution: Verify command availability before making changes
  • Multi-repo scaling: Scripts can now intelligently skip repositories that don’t support specific commands
  • CI/CD integration: Repver can participate in pipeline logic with proper exit codes

This release also maintains full backward compatibility—existing workflows continue to work exactly as before, with the new flag purely adding capability without breaking anything.

Upgrade and Installation

Pre-compiled Binaries

Download the appropriate binary for your platform from the GitHub Releases page:

  • macOS (AMD64, ARM64)
  • Linux (AMD64, ARM64)
  • Windows (AMD64)

Simply replace your existing binary—no special upgrade steps required.

Build from Source

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

Note: Building from source now requires Go 1.25.6 or later (up from Go 1.25.2 in v0.2.1). Pre-compiled binaries are unaffected by this change.

Get Started

Explore the full documentation to learn about all available commands and configuration options. Try out the new --exists flag in your automation scripts today!

This post was AI-generated using the unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M model. Release information sourced from UnitVectorY-Labs/repver, published January 24, 2026. Author: release-storyteller