repver v0.6.3 was released on October 17, 2026. This maintenance release focuses on reliability for users who define multiple replacement targets that touch the same file. The headline improvement is a fix for lost updates when several targets share a path, making batch version updates more predictable and safe.

What’s new

The release corrects a planning issue that caused later targets to overwrite earlier ones when multiple targets referenced the same file. Previously each target was planned against the original disk content, so only the last target’s change would survive for that path.

v0.6.3 introduces command-level planning that composes targets in configuration order against accumulated in-memory content, producing one plan per distinct path. Changes are evaluated entirely in memory before any file or Git mutation occurs. This preserves the intended ordering of replacements and enables dependent replacements within the same file.

The fix is covered by new regression tests for forward and reverse order, interleaved files, trailing no-op targets, and end-to-end CLI scenarios including dry-run and dirty workspace rejection. No configuration changes are required, and existing single-target workflows are unchanged.

The release also updates repver’s own Go toolchain to v1.27.2 and adds CI hardening with official govulncheck SARIF scanning. These changes are internal to the project’s release process and do not affect CLI behavior.

Why it matters

For teams using repver to update version numbers, Docker tags, or other placeholders across documentation, workflow files, and source code, reliability is critical. A common pattern is to update several placeholders in one file, such as a README and a Dockerfile, or multiple version strings within the same manifest. Before v0.6.3, those updates could silently drop earlier changes, requiring manual workarounds.

With the composed planning, users can define multiple targets for the same file with confidence that all replacements will be applied in the order specified in .repver. This reduces manual verification, avoids partial updates, and makes automated version bumps trustworthy for larger repositories.

Upgrade and installation

v0.6.3 is a drop-in upgrade. Download the pre-compiled binary for your platform from the GitHub Release page, or install via go install github.com/UnitVectorY-Labs/repver@latest. No configuration changes are needed. If you previously worked around the same-file limitation by combining patterns or reordering targets, those workarounds remain compatible.

Get the release: https://github.com/UnitVectorY-Labs/repver/releases/tag/v0.6.3

This post was AI-generated. The model used was unsloth/Muse-Glimmer-30B-GGUF:Muse-Glimmer-30B-UD-Q6_K_XL. Reference repository UnitVectorY-Labs/repver, release v0.6.3, date of generation 2026-10-18. Author: release-storyteller