Skip to content

fix: derive CLI version from the build instead of a stale constant#1157

Merged
laurentiu021 merged 1 commit into
mainfrom
fix/cli-version-dynamic
Jun 29, 2026
Merged

fix: derive CLI version from the build instead of a stale constant#1157
laurentiu021 merged 1 commit into
mainfrom
fix/cli-version-dynamic

Conversation

@laurentiu021

Copy link
Copy Markdown
Owner

What

The CLI reported a stale version (Batch 4 of 6, post-feature audit).

Fix

CliRunner.Version was a hardcoded const = "1.49.0" while the build had moved to 1.51.x — so SysManager.exe --version, --version --json, and the --help banner all printed the wrong version to any script parsing them. It now derives from UpdateService.CurrentVersion (the assembly version, set from the csproj single source of truth), formatted to 3 parts. The value can never drift from the build again.

Test

CurrentVersion_MatchesBuildVersion_NeverDrifts asserts the CLI version equals the assembly version, so any future drift fails CI.

Docs

CHANGELOG 1.51.4, version bump to 1.51.4.

Part of the post-feature audit remediation (Batch 4 of 6).

…onstant

CliRunner.Version was a const '1.49.0' that had drifted two minor releases behind
the actual build, so 'SysManager.exe --version' and --help reported the wrong
version to scripts. It now reads UpdateService.CurrentVersion (the assembly
version compiled from the csproj single source of truth), formatted to 3 parts, so
it can never drift again.

Test: CurrentVersion_MatchesBuildVersion_NeverDrifts pins the CLI version to the
assembly version, failing the build on any future drift.
@laurentiu021 laurentiu021 merged commit faabdab into main Jun 29, 2026
4 checks passed
@laurentiu021 laurentiu021 deleted the fix/cli-version-dynamic branch June 29, 2026 12:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant