Two independent failures kept the v0.6.5 installer from being built after
the pipe probe was fixed.
The package job died in "Verify the release commit is on main" with git
exiting 128 on dubious ownership: runner instance 2 leaves _work owned by
SYSTEM while the job runs as `runner`. actions/checkout is unaffected, so
the first plain git call is what fails, and only jobs scheduled onto that
instance see it. Mark the workspace as safe in the three self-hosted jobs.
Neither vcpkg manifest carried a builtin-baseline, so vcpkg resolved ports
against the registry at HEAD and every build depended on a live fetch of
microsoft/vcpkg. When that fetch degraded, the ports simply vanished:
Fetching registry information from https://github.com/microsoft/vcpkg (HEAD)...
fmt does not exist
utfcpp does not exist
Build TSF x64 failed this way twice and passed twice on the same runner,
which is what an unpinned registry looks like. Pin both manifests to
04a9d8e5, the commit vcpkg-lock.json already records as resolved.
The baseline bump in #17 broke main. builtin-baseline names a commit in the vcpkg clone on the
machine, and the one bundled with the Windows runner is shallow, so it does not have a commit from
yesterday:
fatal: path 'versions/baseline.json' exists on disk, but not in '04a9d8e5...'
while loading baseline version for curl
The old baseline worked only because it was old enough to be present locally, which means the
mechanism was going to fail on any sufficiently fresh pin.
Declaring the default registry as a git registry makes vcpkg fetch the pinned commit itself. That is
what MSIME-Windows already does, and MSIME-Engine#17 has now confirmed the same fix on all three
platforms. vcpkg-configuration.json existed here as an empty object, so this fills it in.
The pinned baseline was 66c0373d, committed 2026-01-16 and 2870 commits behind. Nothing was watching
it: the dependabot template in this org declares only github-actions and gitsubmodule.
Eight ports move. The pairing worth watching is spdlog 1.15.1 to 1.17.0 alongside fmt 11.0.2 to
12.2.0, since spdlog builds against fmt and a mismatched pair is a familiar way to break a build.
webview2 also moves a long way, 1.0.2277.86 to 1.0.4191.47.
CI builds Release here but runs no tests, so a green check means it compiles and nothing more. The
WebView2 loader and the candidate window are the parts to exercise by hand before trusting this.
Lu Fan(SonnyCalcr)