chore: bump version to 2026.7.29.2 - #310
Merged
Merged
Conversation
The skill told you to bump all four version locations in one commit. Two of
them — `.xlings.json` `workspace.mcpp` and `ci-fresh-install.yml` `MCPP_PIN` —
are not "the current version" at all: they are the already-published version CI
BOOTSTRAPS FROM. Moving them to the version being released makes every job try
to `xlings install` something that does not exist yet.
The skill already documented the correct sequence further down ("bootstrap pin
收尾"), so step 2 contradicted it. Git history agrees with the tail: fd27314
bumped only mcpp.toml and fingerprint.cppm, leaving the pin on 2026.7.28.2.
Splits the four locations by the question each answers. The first group moves
every release. The second is a bootstrap origin that does NOT track releases —
lagging several versions is the normal state, the release flow leaves it alone,
and advancing it is an occasional deliberate act whose one hard precondition is
that the target version is already published and indexed.
Also routes the bump through a PR (mcpp-contributing forbids direct pushes for
version bumps too) and adds two failure rows: the all-red bootstrap symptom,
and the stale `--version` you get from `ls | head -1` when the target/
fingerprint directory changed with the version.
speak-agent
force-pushed
the
chore/bump-2026.7.29.2
branch
from
July 29, 2026 09:47
533b6a5 to
49ec1fb
Compare
Sunrisepeak
approved these changes
Jul 29, 2026
Sunrisepeak
left a comment
Sunrisepeak
left a comment
Member
There was a problem hiding this comment.
Version bump verified: check_version_pins.sh OK (building 2026.7.29.2, bootstrap pin stays 2026.7.29.1), --version matches. Skill correction matches git history.
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.
Summary
发版
2026.7.29.2(当天第二个迭代版;.0保留给正式/稳定版),外加一处发布规范文档修正。本版内容:#309 —— SemVer 约束改走索引路由,项目
[indices]里的包不再"写死版本能解析、带约束就挂"。1. 版本号 bump
只改第一组两处:
mcpp.toml与src/toolchain/fingerprint.cppm。bootstrap pin(.xlings.json的workspace.mcpp、ci-fresh-install.yml的MCPP_PIN)仍停在 2026.7.29.1 —— 新版尚未发布,提前挪会让每个 CI job 去xlings install一个不存在的版本;按惯例(fd27314 只改两处,fde3b70 事后收尾)在发布并进索引后单独前移。2. 修正 mcpp-release skill
skill 第 2 步写的是"四处一起 bump",与它自己后半程的「bootstrap pin 收尾」自相矛盾,也与 git 历史不符 —— 照着做会让全部 CI 红在 bootstrap。
改为按各自回答的问题拆成两组:第一组(
mcpp.toml+fingerprint.cppm)每次发版必改;第二组(.xlings.json+MCPP_PIN)是 CI 的自举起点,与本次发布无关,不需要每次发版都动 —— 落后几个版本是正常状态,发布流程默认不碰它,真要前移唯一的硬前提是目标版本已发布并进索引。另外 bump 改走 PR(
mcpp-contributing同样禁止版本 bump 直推 main),并补两条失败排查:package 'mcpp@X.Y.Z' not found→ pin 提前 bump 了--version显示旧版本 →target/<triple>/<指纹>/指纹随版本变,ls | head -1取到了上次构建check_version_pins.sh的实际语义也在文档里写清楚了:它只要求两处 pin 彼此相等且不新于正在构建的版本,并不要求等于它。Test plan
bash .github/tools/check_version_pins.shOK(building=2026.7.29.2,bootstrap=2026.7.29.1)mcpp build通过,mcpp --version→mcpp 2026.7.29.2tests/e2e/01_help_and_version.sh通过(它交叉比对 mcpp.toml 与 --version)