chore: bootstrap from 2026.8.2.1 - #333
Merged
Merged
Conversation
The package is published and verified on both mirrors, so the self-host build can start from it. Deliberately a separate change from the version bump: moving this pin before the release exists sends every CI job to install a version that is not there yet.
The implementation plan now carries the findings the plan itself could not have predicted — the response-file path form, the clang miscompilation, the BMI-flag quoting, the deployment target's scope, the persisted-target precedence rule, and the three ways the Visual Studio masking looked like it worked when it had not.
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
1 participant
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.
Routine post-release pin bump. 2026.8.2.1 is published, mirrored to both xlings-res ends (sha256 verified by independent download), indexed (xim-pkgindex#476), and installs cleanly from the index — verified by running e2e 179 / 181 / 89 / 112 against the released binary.
The bootstrap pin moves only now, after the package is fetchable: bumping it alongside the version would point every CI job at a release that does not exist yet.