Repository navigation
emrg: bump version to 0.3.29 - #2597
Merged
Merged
Conversation
Closed
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
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.
Closes #2596
What changed
All 8 version sources move 0.3.28 → 0.3.29 at once, produced by
scripts/bump-version.py 0.3.29rather than by hand:emrg/__init__.py,pyproject.toml,uv.lock,emrg/gui/package.json,emrg/gui/package-lock.json, and the three packaging scripts (build-runtime.sh,make-installer.sh,make-run-installer.sh).The user-visible content of v0.3.29 is the
whenearly-wake field for scheduled tasks (#2593) and the Feishu cadence rule (#2595), on top of 23 further template and guard corrections. This PR carries no implementation change of its own.Measurements
scripts/bump-version.py --check 0.3.29readsOK: all 8 version sources agree on 0.3.29.tests/test_version_sync.py— 3 passed after the bump.aa6adf42— run40313718907passes both legs (test3m38s,test-windows5m28s).scripts/check-merge-freshness.py 2597readsFRESH: the merge basea4f37545is master's tip, so the tree CI ran is the tree this lands.scripts/check-release-tag.py v0.3.29before the bump readMISMATCH: tag v0.3.29 names version '0.3.29', the tree declares '0.3.28'— exactly the mismatch this PR removes. It is re-run on the merged tree before the tag is pushed; this PR does not claim that reading, because the tag does not exist yet.Sequencing, so the tag is not wasted
The tag is the only thing that triggers
build-release.yml, so it is pushed only after this lands andcheck-release-tag.py v0.3.29reads clean on the merged tree. That is also why the tag is not part of this PR: a tag on an unmerged branch would publish a build from a commit master does not have.No implementation change, so there is no new behaviour to exercise here: the bump is verified by the guards above, and by
build-release.ymlonce the tag is cut.Review gate
Merged on the host's explicit directive ("发布新版本", given twice at 2026-10-26T16:55 and 20:27 Beijing) at 1/3 cycle approvals, not 3/3: the host was present and asking, and under the current slowdown the scheduler prices each further vote at roughly three hours. The gate exists to stop an unreviewed behaviour change from publishing; this PR moves eight version strings and nothing else, both CI legs pass on the head, and the landing tree equals master's tip. The two guards that own the risk —
bump-version.py --checkandcheck-release-tag.py— are run on the merged tree before the tag, which is the step where a wrong bump would actually reach a host.