Tronador CLI v0.2.7: Release-Safe Project Automation

Created: August 14, 2026
Updated: August 18, 2026

Cloud Ops Works has released tronador-cli v0.2.7, the current patch release in the v0.2 line. This update covers every improvement shipped after v0.2.3: safer repository upgrades, clearer IaC version selection, quieter and repository-aware GitVersion behavior, exact-HEAD-tag version detection, and previewable evaluated version-file deltas.

The project and package-manager package are named tronador-cli, while the installed executable is tronador. For example, install with brew install cloudopsworks/tap/tronador-cli, then run tronador version.

What changed from v0.2.3

v0.2.3-clean is a published tag with no release-note body, so this article does not attribute changes to it.

Safer repository upgrades

Repository upgrades now preserve files that belong to the repository rather than the template machinery. In particular, v0.2.4 preserves existing Dependabot configuration and template-guidance files, avoiding unnecessary rewrites of local maintenance policy and contributor instructions during an upgrade.

That matters when a repository is upgraded over time: the CLI can bring in supported template changes without treating every checked-in file as disposable generated output.

More deliberate IaC version selection

IaC module discovery and upgrades have become more explicit about release tiers. The CLI can include alpha and beta prerelease channels when they are requested, while normal selection remains focused on the intended release scope. Upgrade reporting follows the same requested patch, minor, or major tier instead of presenting unrelated candidates as equivalent choices.

When a requested major-level target has no direct match, the CLI can fall back to the highest eligible minor target within that same major line. This keeps upgrade selection useful without silently crossing a major-version boundary.

Before changing a repository, inspect the published options:

tronador repos available --workdir ../my-service

Then choose the upgrade scope deliberately:

# Upgrade within the current compatible patch line.
tronador repos upgrade --workdir ../my-service

# Move to the latest compatible major-line version.
tronador repos upgrade major --workdir ../my-service

# Select a reviewed target explicitly.
tronador repos upgrade vX.Y.Z --workdir ../my-service

GitVersion behavior that follows the repository

Versions should reflect the repository being operated on, not defaults embedded in a tool invocation. v0.2.5 honors repository-local GitVersion configuration and keeps its output quiet, so normal command output stays focused on the requested operation.

v0.2.6 extends that work for release states: when the exact HEAD commit is tagged, project version detection recognizes that tag and preserves GitVersion release tags. This avoids losing release context when repository lifecycle operations run on an already-released commit.

Preview evaluated version-file changes

Version operations can now preview the evaluated delta for version files before writing it. This makes the intended repository change visible during planning and review, so an operator can confirm the exact version-file update before a lifecycle action modifies the working tree.

Upgrade and verify

Use your preferred installation channel, then verify the installed binary:

# Linux or macOS shell installer
curl -fsSL https://raw.githubusercontent.com/cloudopsworks/tronador-cli/master/scripts/install.sh | sh

# Homebrew
brew install cloudopsworks/tap/tronador-cli

# Verify the installed release
tronador version

For Windows PowerShell, run:

iwr https://raw.githubusercontent.com/cloudopsworks/tronador-cli/master/scripts/install.ps1 -UseB | iex
tronador version

See the installation guide for package-manager, verification, upgrade, and uninstall details. For the v0.2 foundations introduced before this patch wave, read the v0.2.3 announcement.