Skip to main content

Release versioning: evidence (run bower-version-20261103-063441)

What was run: the release-versioning change in PR #175, documented in release versioning. No AWS or Azure resources were needed or created; the CI install jobs on Linux and Windows are the live proof.

Local checks (macOS arm64, .NET SDK 10.0.403, Rust stable)​

CheckResult
dotnet build Bower.sln -c ReleasePass, 0 warnings
dotnet test --solution Bower.sln -c ReleasePass: 2,204 total, 0 failed, 2 skipped (Windows-only event log tests)
dotnet format --verify-no-changesPass
Build stamped with -p:BowerVersion=0.1.0-dev.362 -p:BowerBuildNumber=362bower --version → bower 0.1.0-dev.362; Bower.Collector --version → bower-collector 0.1.0-dev.362; BowerVersionTests pass with BOWER_EXPECTED_VERSION=0.1.0-dev.362 and fail (1 of 5) with 0.1.0-dev.999, so the check bites
Invalid versions (0.1.0-beta.1, 0.1.1 against VERSION 0.1.0, build number 65536)Build fails with the documented message
cargo fmt --check, cargo clippy --workspace --all-targets -D warnings, cargo test --workspace --no-fail-fastPass; unstamped binaries print bower 0.1.0-dev.0 / bower-collector 0.1.0-dev.0
python3 -m unittest discover -s tools/ciPass, 33 tests (incl. 12 in test_version.py)
python3 -m unittest discover -s lab/aws/testsPass
mkdocs build --strict and tools/docs/check_links.pyPass, 108 pages
actionlint, zizmor --min-severity highClean
PSScriptAnalyzer on deploy/installers/windows (5.1 and 7.4 syntax)0 findings

Failed attempts kept for the record:

  • The first MSBuild validation regex used \. and \d; MSBuild on macOS/Linux turned the backslashes into /, so the build rejected 0.1.0. Fixed with character classes.
  • The first full .NET run failed PolicyParityVectorTests.LoaderVectors_MatchCSharpOutcomes: YamlDotNet error text includes Version=1.0.0.0 of the assembly, and the change had moved AssemblyVersion to 0.1.0.0. AssemblyVersion is now pinned to 1.0.0.0.
  • The first full Rust run failed the status key-order test and the Lambda parity test (Lambda used CARGO_PKG_VERSION). Both now use the release version.

CI (the live proof)​

The version, build-test, rust, docker, package-linux, package-windows, install-linux (Ubuntu deb, Rocky Linux 9 rpm) and install-windows (Windows Server MSI) jobs of the PR's CI run are the proof for upgrade, refused downgrade, explicit rollback and same-version reinstall. Their results are in the PR checks; a result not shown there as passed is not passed.

CI results, first head (16c7cc2, run 369)​

CI run 41590823537: every job passed. From the job logs:

  • install-linux, Ubuntu (deb): upgrade 0.1.0-dev.0 → 0.1.0-dev.369; package, CLI, collector and /v1/status all reported 0.1.0-dev.369. dpkg -i and apt-get install --allow-downgrades were refused with bower-collector: refusing to downgrade from 0.1.0-dev.369 to 0.1.0-dev.0. …; package, PID, settings and queue unchanged; explicit rollback and same-version reinstall passed.
  • install-linux, Rocky Linux 9 (rpm): rpm -U refused natively (… which is newer than … is already installed); rpm -U --oldpackage and dnf downgrade refused by the guard; state unchanged; rollback and reinstall passed.
  • install-windows, Windows Server: upgrade to ProductVersion 0.1.369; registry, CLI, collector and /v1/status reported 0.1.0-dev.369. The older MSI exited 1603 with Product: Bower Collector -- A newer Bower Collector is already installed, so this older version (0.1.0-dev.0) was not installed. …; state unchanged; the same MSI again was a no-op (same PID); BOWERALLOWDOWNGRADE=1 rolled back keeping bower.env, the secret and the queue.

Council round 1 fixes (second head)​

  • VERSION is 0.1.1, above the 0.1.0 that pre-scheme builds hard-code; the fleet console orders versions semantically (dev < rc < release, numeric N).
  • The MSI decides downgrades semantically with the installed VersionKey; CI adds a fixture built "later" (ProductVersion MAJOR.MINOR.65535) but semantically older, which must be refused. tools/ci/test_version.py proves the key order and that build.ps1 and version.py compute the same keys.
  • :latest only for final release tags; images use build number 0; version fails non-tag builds after v<VERSION> is tagged; the Rust job runs the version test against the stamped version (locally: stamped run passes, a mismatched expectation fails); the Functions collector reports the build version.

Local checks on the second head: dotnet test 2,214 total, 0 failed, 2 Windows-only skips; cargo test --workspace unstamped and stamped (BOWER_VERSION=0.1.1-dev.5) pass; tools/ci tests pass; strict docs build and link check (109 pages), actionlint, zizmor, shellcheck and PSScriptAnalyzer clean. CI results for that head are in the PR checks.

Limits​

  • Kubernetes, AWS EC2 and Azure VM hosts use the same packages and images; they were not run separately. arm64 packages are built, not install-tested.
  • Upgrade tests run with an almost empty queue.

Cleanup audit​

No cloud resources were created for this run: no AWS or Azure API calls were made, so zero resources with RunId bower-version-20261103-063441 exist in either account.