Repository navigation
bootstrap from 2026.10.10.2; CI builds the tree with the pinned mcpp as a developer does, and with the newest release - #796
Merged
Conversation
The post-release pin (docs/92-release.md §4): the index pointer serves xim-pkgindex d6f6fd5 (#950). A developer's `xlings install` in this tree and every CI bootstrap take the newest release, whose archives bundle xlings 2026.10.10.2.
…lone does, and so does the newest release while the pin lags it .xlings.json names the mcpp a clone builds with: inside the checkout the shim runs no other. A pinned mcpp older than the manifest warned about a key it did not know, dropped it and exited 0 (2026.9.24.1 against [test] windows_code_page), so no job failed when the pin had to move. - build.yml: the self-host build runs `mcpp build --strict`. - ci-bootstrap.yml developer (Linux, macOS, Windows, no cache): `xlings install` in the checkout, the shim's version equals the pin, `mcpp build --strict`, the binary reports mcpp.toml's version. - ci-bootstrap.yml latest (Linux): the newest release builds the tree with --strict while the pin lags it; skipped when they are equal. - docs/92 §4 (en, zh): the pin moves when the tree needs it, and these jobs say when.
Sunrisepeak
changed the title
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.
Bootstrap pin
.xlings.json2026.10.8.1 → 2026.10.10.2. The index pointer serves xim-pkgindex d6f6fd5 (#950).The pin is checked, not chased
.xlings.jsonnames the mcpp a clone builds with. Inside the checkout, themcppshim runs that version and refuses to run untilxlings installhas installed it (measured in a clean HOME). The pin moves when the tree needs something the pinned mcpp lacks.Until now, nothing failed when that moment came. A pinned mcpp older than the manifest warns, drops the key and exits 0. Measured with pin 2026.9.24.1 on this tree:
mcpp buildwarning: [test] has unsupported key 'windows_code_page' (ignored)mcpp build --stricterror: [test] has unsupported key 'windows_code_page' (ignored)Changes:
build.yml: the self-host build on the four hosts runsmcpp build --strict.ci-bootstrap.ymldeveloper(Linux, macOS, Windows, no cache), as a fresh clone:xlings installin the checkout (project scope, no-g);mcpp build --strict;mcpp.toml's version.ci-bootstrap.ymllatest(Linux): the newest release builds the tree with--strict. It runs only while the pin lags the newest release and is skipped when they are equal.docs/92-release.md§4 (en, zh) andcheck_version_pins.sh: the pin moves when the tree needs it, and these jobs say when. Moving it after every release is no longer required.