Semantic versioning (1.0.0) and MSI-based agent upgrades #19
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Semantic versioning, the first semantic release (1.0.0), and MSI-based agent upgrades.
Semantic versioning
X.Y.ZfromvX.Y.Ztags. The next version is computed from conventional commits by semantic-release in dry-run mode (pinned inbuild/release). Our script creates the tag and the Gitea release with notes.v0.1.0is on the last calendar release (v2026.10.23.2331). This PR carriesBREAKING CHANGE, so the first release is 1.0.0. I checked this with a simulated merge.X.Y.Z.N(commits since the tag), with no prerelease labels, so Windows, MSI and AssemblyVersion take them as they are. InformationalVersion isX.Y.Z+sha.mainreleases only when a release is due.release.ymlbuildsX.Y.Z, tags it, publishes it, and pushes images:X.Y.Zand:latest.:X.Y.Z.Nand:latest.:devand:X.Y.Z.N-dev. This is a change: they no longer push the bare version tag.AllowDowngradesplus a FindNewerRelease custom action (DTF) that maps old 26.x MSI versions back to the calendar version. A 1.0.0 MSI therefore upgrades over 26.x, while a real accidental downgrade is refused unlessALLOWDOWNGRADE=1is passed.REINSTALLMODE=amus, so 1.x files replace 2026.x-stamped ones.package.jsonbeside it, for rollbacks.MSI-based agent upgrades
msi.dllin-process (MsiSetInternalUI,MsiEnableLogW,MsiInstallProductW,REBOOT=ReallySuppress). No msiexec or PowerShell is involved, and the runner survives the MSI stopping both services.ALLOWDOWNGRADE=1: the kept copy, or the server's copy for that version.Testing
ALLOWDOWNGRADE=1🤖 Generated with Claude Code
KeepInstallerPackage now gets the package's full version ([UNIFIEDVERSION]) and writes package.json ({"version","sha256"}, camelCase) beside the copy, under a temporary name and renamed, so the agent finds a kept MSI's version without opening it. The copy keeps the original file name (ExecuteR-Agent-<version>.msi). UNIFIEDVERSION stays the version the agent reports: the agent's MSI upgrades read it from the MSI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>