chore: bump version to 2026.8.16.3 - #443
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ships the round that made
msvc@<toolset>actually work end to end, plus #437.What this release contains
The managed MSVC toolchain now completes its whole lifecycle on a real Windows runner:
Getting there took nine layers, each only reachable once the one before it was fixed — and every layer had been green in CI:
installed()checkedcl.exeonly, then directories onlykernel32.lib; noum/sharedheaders, norc/mtLNK1104removefailed on Windows; the error did not say which filevctip.exeheld the payload; not installing it ≠ fixing machines that had itAlso fixed here (from the architecture review,
.agents/docs/2026-08-16-toolchain-architecture-review.md):mcpp doctorcould not see an installed msvc toolset thattoolchain listshowed — the pre-fix(toolchain): an installed msvc toolset did not appear intoolchain list#436 layout lookup, fourth copyhas_usable_msvc()gated three decisions on "this machine has VS", diverting a box with a pinned toolset to mingw/MDbuild could not start on a clean Windows box:vcruntime140.dllis not an OS component, and the payload's copy was downloaded and never usedtoolchain defaultaccepted a directory that merely existsAnd #437: on macOS any project carrying a
build.mcppfailed to build, because the main build forces-fuse-ld=lldand the host helper did not — same toolchain, same environment, two link paths disagreeing.Changelog accuracy
One entry in
[Unreleased]described the removal fix as renaming the payload directory. That premise was wrong and CI disproved it: Windows renames an open file happily and refuses to rename a directory containing one. The entry now describes what actually ships — move the files aside, delete the emptied tree, and treat "no files remain" as removed.