What’s New

Today we’re excited to release repver v0.5.0, a feature-rich update that brings powerful new capabilities for managing version numbers across your repositories. Released on February 20, 2026, this release introduces intelligent version transformation and input validation—two features that make version management safer and more flexible than ever.

What’s New

Flexible Version Transformation

The headline feature in v0.5.0 is the new transform capability. Previously, if you needed to update version numbers in different formats across multiple files (like “1.26.0” in GitHub Actions but “1.26” in go.mod), you had to manage this manually or maintain separate configurations.

Now, repver can automatically transform a single input version into the format each file needs. Define your version once as semantic versioning (e.g., “1.26.0”), and repver will apply the right format to each target:

params:
  - name: version
    pattern: "^(?P<major>\\d+)\\.(?P<minor>\\d+)\\.(?P<patch>\\d*)$"

targets:
  - path: "go.mod"
    pattern: "^go (?P<version>.*) // GOVERSION$"
    transform: "."  # → "1.26"
  - path: ".github/workflows/build.yml"
    pattern: "go-version: '(?P<version>.*)' # GOVERSION$"
    transform: ".."  # → "1.26.0"

Input Validation for Safety

Version typos can be costly—imagine running a command that updates five files with “1.2b.0” instead of “1.26.0”. With v0.5.0, repver validates your input against patterns you define before making any changes:

params:
  - name: version
    pattern: "^(?P<major>\\d+)\\.(?P<minor>\\d+)\\.(?P<patch>\\d*)$"

If the provided version doesn’t match the semantic versioning format, repver stops immediately with a clear error message. No partial updates, no rollback needed.

Enhanced Error Messages

Validation failures now provide descriptive feedback:

  • Invalid parameter values that don’t match your pattern
  • Duplicate parameter names within a command
  • Transform placeholders referencing non-existent named groups
  • Better syntax guidance for regex capture groups

Documentation Improvements

The v0.5.0 release includes substantial documentation enhancements:

  • Comprehensive configuration reference in docs/CONFIGURATION.md
  • Practical examples with common patterns in docs/EXAMPLES.md
  • Updated process flow diagrams showing the new validation step

Why It Matters

These features address real pain points in version management workflows. The transformation feature eliminates the guesswork of formatting versions for different files, while validation prevents the nightmare of propagating typos across your repository. Together, they make repver more powerful and safer to use.

For existing users, there’s great news: v0.5.0 is fully backward compatible. The new features are opt-in through your .repver configuration. If you don’t add params or transform, your existing setup works exactly as before.

Upgrade Instructions

Upgrading to v0.5.0 is straightforward:

Using Go Install:

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

Download a Binary: Visit the v0.5.0 release page to download pre-built binaries for your platform.

Note: Building from source now requires Go 1.26.0 or later, but pre-built binaries include all dependencies.

Looking Ahead

With v0.5.0, repver continues its evolution as a robust tool for automated version management. The addition of validation and transformation capabilities represents a maturation of the tool’s core value proposition: making repetitive version updates reliable and maintainable.

We’d love to hear how you’re using these new features. Check out the full release notes for all the details, and happy versioning!

This post was AI-generated by unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M on February 20, 2026. Source: UnitVectorY-Labs/repver. Author: release-storyteller