Skip to content

Release Notes

Rod Christiansen edited this page Oct 8, 2026 · 4 revisions

Release Notes

Every BootstrapMate for Windows release, newest first, with the changes that went into it. Use this page to work out which version introduced a behaviour you are seeing, and what upgrading will change. Each entry lists the commit subjects in that release; where a change altered behaviour an administrator would notice, that is called out.

Versioning and artifacts

Releases are tagged vYYYY.MM.DD.HHMM — the build timestamp, not semantic versioning. There is no notion of a major, minor or patch release; a later tag is just a later build. The tag date shown below is when the tag was created, which can sit a few hours either side of the timestamp encoded in the version string.

The MSI ProductVersion carries the same stamp in the YY.M.DDHH.MM form Windows Installer can compare; everything else carries the full stamp. See Building and Signing.

Pushing a v* tag runs the release workflow, which publishes a GitHub Release containing, for each of x64 and arm64:

  • BootstrapMate-<arch>-<version>.msi
  • BootstrapMate-<arch>-<version>.zip, containing managedbootstrapinstall.exe and the GUI

Those artifacts are unsigned. Sign them with your own code signing certificate before you distribute them, or build locally with build.ps1, which signs as part of the build. The release notes generated by the workflow say the same thing.

On main, not yet released

ea02e50 Read settings from the 64-bit registry only, and keep credential headers where users cannot read them (#59)

Settings and policy are read from the 64-bit registry view only. The MSI removes the stale WOW6432Node\BootstrapMate\Settings key, and the CLI removes it once and logs the value names it removed. AuthorizationHeader and ReportingHeader live in HKLM\SOFTWARE\BootstrapMate\Secrets, readable only by SYSTEM and Administrators; an elevated run moves a header found in policy or settings there and blanks the readable copy. The app saves headers there and never passes one on a command line, and --headers is redacted from every logged command line. See Preferences.

The next v* tag ships this. Until then the latest release reads headers from the policy and settings keys directly.

v2026.10.05.1229

97447d0 Run a baseline for every new build, retry interrupted ones at once, and lock down the data directory b6d2d05 Make the GUI Prefs tab read-only until unlocked as administrator

A BootstrapMate version that has not yet completed a baseline gets one regardless of BaselineMinIntervalHours; an interrupted baseline runs again at the next trigger. baseline.json gains tool_version and attempt_version. C:\ProgramData\ManagedBootstrap gets its own ACL from the MSI, and every elevated run resets it and removes anything a non-administrator created there.

Settings come only from HKLM: the CLI reads no per-user settings key and has no --save-settings-file. The app's Prefs tab is read-only until Unlock relaunches it as administrator. See Managed Bootstrap Install App.

v2026.10.05.1124

d1232f8 Throttle baseline runs, record interrupted runs, and put the hour in the MSI version

Baseline runs are throttled by baseline.json and the BaselineMinIntervalHours setting (default 144). A run that finds the previous one still running records it as interrupted. The MSI ProductVersion is YY.M.DDHH.MM, so two builds made in different hours of the same day upgrade each other. See Preflight and Baseline.

v2026.10.05.0926

a92bdcf Route MSIs correctly, verify payload hashes, honour or remove dead settings, make --status read-only (#54) 1c5d4df Rename the GUI app to Managed Bootstrap Install and fix its missing icon (#55)

An item's hash (SHA-256) is verified for every type. Chocolatey keeps checksum verification on unless an item sets ignoreChecksums. A Cimian-built MSI with arguments, and the sbin-installer package under any name, go to msiexec. DryRun refuses to run; NetworkTimeout, DialogIcon, EnableDialog, SilentMode and VerboseMode take effect; FollowRedirects and Reboot are removed. The CLI's manifest is asInvoker, and --status needs no elevation.

The app is Managed Bootstrap Install.exe, with that name in the window title, Add or Remove Programs and the Start Menu. The CLI name, install folder, registry keys, UpgradeCode and task name are unchanged.

v2026.10.04.1228

44826e6 Record each run's mode and outcome; fix the 100-second download timeout (#52)

last-run.json records each run's mode, status and items, and --last-run prints it as one line. session.json carries run_type. Package downloads stream with no overall timeout and retry stalls, network errors and 5xx responses.

v2026.10.03.1241

2b0a646 Stream a GUI run's output from its session log (#50)

The app's Run tab finds and tails the run's session bootstrap.log.

v2026.10.03.1142

3994b75 Add baseline mode, chosen by a preflight stage (#49) 8bc7f32 Correct the shipped example, README and build configuration 87ec441 Handle every argument the entry point is given 81d36ce Close unterminated elements in the ADMX and ADML policy templates f845681 Write status where every reader looks for it 43a5d13 Report a run's outcome truthfully c596483 Stop damaging machine state during Chocolatey repair and nightly runs

The largest behaviour change in the project's history. Administrators will notice:

  • A preflight stage chooses Skip, Baseline or Provision. See Preflight and Baseline.
  • Exit codes: 0 success, 1 usage or manifest error, 2 packages failed, 3 elevation not obtained. A run with failed packages exits 2.
  • Status is written under HKLM\SOFTWARE\BootstrapMate, where --status, --clear-status and the detection scripts read it. Status from HKLM\SOFTWARE\Cimian\BootstrapMate is migrated.
  • An unrecognised argument exits 1; --dry-run refuses to run; --version/-V work in any position.
  • session.json records each run's outcome.
  • The ADMX and ADML parse.
  • The self-heal task runs without --force, and Chocolatey repair preserves the machine PATH's registry type and removes only Chocolatey's own directory from it.

v2026.09.04.0436

d77f76c Give each run a session directory with structured events (#21, #22) 519dd72 Fail the run when its packages failed (#23)

Two changes an administrator will notice.

Each run writes to its own directory, C:\ProgramData\ManagedBootstrap\logs\<yyyy-MM-dd>\<HHmmss>\, holding bootstrap.log beside events.jsonl and session.json rather than a single flat file at the logs root. Anything that globbed logs\*.log needs to recurse. Retention drops day directories past the 30-day window and session directories past a cap of 100, and still sweeps the flat files the old layout left. See Logging and Reporting.

A run whose packages failed records it. Package failures are caught so the run continues, and they are carried out of the loop: the phase is marked Failed with the failed names, LastRunVersion is not written, the log ends BootstrapMate completed with N failed package(s), and the run summary POSTs success: false. The process exit code in this release stayed 0; v2026.10.03.1142 added exit code 2.

v2026.09.03.0605

e9c0498 Stamp output captured from a package's own process (#20)

Output captured from an installer's own stdout and stderr is written one stamped line at a time rather than as a single stamped block, so every line of package output carries a date. See Logging and Reporting.

v2026.09.02.0559

61c8231 Write log lines in the shared session log format and fix the -v flag (#19)

The log file adopts the shared session log format, and -v means verbose. In this release -V printed the version only as the first argument; v2026.10.03.1142 accepts it anywhere.

v2026.08.20.1457

1894d18 Expire session logs older than the retention window (#17)

Session logs are pruned at startup against a 30-day retention window, based on each file's last write time, so the log directory stops growing without bound. Superseded in part by v2026.09.04.0436, which prunes session directories as well.

v2026.07.21.1543

5d3d40d Scope the policy Authorization header to the manifest host (#13)

The configured Authorization header is attached only to requests whose host matches the manifest's host. Package downloads from any other host go out without it. This fixes downloads that failed with Download failed: Forbidden because a storage backend rejected an unvalidatable Authorization header on an otherwise public object.

v2026.07.21.1306

04e72ac Serialize concurrent sessions; demote critical-package retry note to Info (#12)

Concurrent invocations serialize behind a global mutex instead of colliding, and the critical-package retry notice is logged at Info rather than as a warning.

v2026.06.23.0617

050e6bf installer: wait on _MSIExecute mutex instead of failing on 1618 (#9)

MSI error 1618, another Windows Installer transaction already running, is not a package failure. BootstrapMate waits on the Global\_MSIExecute mutex before each launch, and a 1618 result is retried without consuming the retry budget. See Retries and Timeouts.

v2026.06.22.1233

07d998d Rename CLI executable to managedbootstrapinstall.exe (#8) b19f5fc Upgrade GitHub Actions to Node24-compatible versions 742573a Post a vendor-neutral run summary on completion (#7) 7974e4e Rename policy detector and references to Management (#6) 5930b1e Verify installer Authenticode signatures before running elevated (#5) 5c15b89 Strip user attribution from generated release notes

Two changes matter operationally. The command-line executable is managedbootstrapinstall.exe; the MSI removes the earlier installapplications.exe on install, so scripts and scheduled tasks referencing the old name need updating. And MSI and EXE packages are Authenticode-verified before they are run elevated — see Security and Package Verification. A run summary can also be POSTed to a configured reporting endpoint on completion.

v2026.06.04.1150

076a7be wxs: delegate post-install to SelfHeal scheduled task (avoids MSI mutex deadlock) (#4)

The MSI starts the BootstrapMate Self-Heal scheduled task instead of the executable, because a deferred custom action that started the executable deadlocked against the Windows Installer mutex the install itself held. See Deployment.

v2026.06.03.2126

2160039 wxs: avoid -- in XML comment body (WIX0104) fe87294 config: HKLM Settings fallback + baked-in default URL; MSI registers self-heal task and runs --force --no-dialog

Machine-scope settings under HKLM join the configuration chain, a default manifest URL is compiled into the binary, and the MSI registers the daily self-heal scheduled task. See Preferences.

v2026.05.28.1943

68403ce ci(release): drop duplicate TZ env key (broke YAML parse) 7899695 fix: Start Menu shortcut + KB display for sub-MB downloads (#3) 9b98d86 release: drop "for Windows" suffix from title 239d30b release(ci): styled release notes + Vancouver timezone

v2026.05.09.1757

e949260 fix(msi): ship WinUI 3 GUI; pick host-arch makepri.exe (#2) e815814 Split combined release.yaml into ci.yml + release.yml

The WinUI 3 app ships inside the MSI from this release.

v2026.03.08.0733

0bb5dc2 docs: Add SignTool signing instructions to GitHub Release notes

The first tagged release. Everything before it is untagged development, including the initial WinUI 3 GUI, the release workflow, YAML manifest support, the progress dialog, and the switch to OSArchitecture for architecture detection so an x64 binary under ARM64 emulation reports ARM64.

Between this tag and v2026.05.09.1757, notable untagged work included f2258eb Attach AuthorizationHeader from policy to all HTTP requests, 7d4956d Prefer sbin-installer for cimipkg-built MSI packages, eff4310 Mark .pkg installation case for sunset in bootstrap, 622dc66 Resolve conflicts: complete Intune CSP/OMA-URI refactoring, remove run.ps1 and BootstrapUrl approach, and c80f4cc fix(build): reliable signtool resolution on clean Windows SDK hosts (#1).

Future releases

Each new v* tag adds a section to the top of this page, with the tag, the commits it contains, and a note on any change that alters behaviour an administrator would notice.

See also

Clone this wiki locally