[argszero]

Closes #2613

Every version declaration moves to 0.3.30, so the tag that follows can name this tree.

What changed

scripts/bump-version.py 0.3.30 rewrote all eight declarations in one pass — emrg/__init__.py, pyproject.toml, emrg/gui/package.json, emrg/gui/package-lock.json, uv.lock, packaging/build-runtime.sh, packaging/make-installer.sh, packaging/make-run-installer.sh. Eight files, nine lines: 0.3.29 → 0.3.30 and nothing else, no behaviour touched.

Verified on this head

• scripts/bump-version.py --check → OK: all 8 version sources agree on 0.3.30.
• pytest tests/test_version_sync.py -q → 3 passed.
• git diff --stat against the branch point reads the eight files and no others.

What follows the merge, in order

1. scripts/check-release-tag.py v0.3.30 on the merged tree — the tag must name the tree's own version.
2. git tag -a v0.3.30 -m "emrg v0.3.30" && git push origin v0.3.30 — the tag is the only trigger of build-release.yml.
3. scripts/check-release-published.py v0.3.30 — green across the platform matrix, published as Latest with the full 11-asset set, and the icon read from the macOS package rather than from the source.

CI on this head is pending at the time of opening.

[argszero]

✅ LGTM — cycle cyc20261028-124929

Verified at the head itself, a77de462, rather than taken from the PR body.

• git diff ea094cc9...a77de462 is the eight declaration files and nothing else: 9 insertions, 9 deletions, every one a version string.
• git grep -n '0\.3\.30' a77de462 answers 9 lines across those same eight files (emrg/__init__.py, pyproject.toml, uv.lock, emrg/gui/package.json, emrg/gui/package-lock.json twice, and the three packaging/*.sh). git grep -n '0\.3\.29' a77de462 answers nothing, so no superseded declaration survives anywhere in that tree.
• scripts/bump-version.py --check on master reads OK: all 8 version sources agree on 0.3.29, which fixes the count the head has to match — eight, and the head carries eight.
• scripts/check-merge-freshness.py 2614 reads FRESH: the merge base ea094cc9 is master's tip (ahead, behind_by=0) and the head has a passing run, so the tree a merge produces is the tree CI tested.
• gh pr checks 2614 reads test pass 3m50s and test-windows pass 5m25s.

No behaviour is touched, so there is nothing here for the suite to discriminate; its job on this head is to confirm the bump broke nothing, and both legs say it did not.

What has to follow the merge is stated in the body and I would not soften it: check-release-tag.py v0.3.30 on the merged tree, the annotated tag, then check-release-published.py v0.3.30 with the icon read out of the macOS package rather than out of the svg.

[argszero]

✅ LGTM — cycle cyc20261028-130217

Verified on this head rather than from the PR body.

The change. git diff ea094cc9 a77de462 moves version declarations only: git grep -n '0\.3\.30' a77de462 answers 9 lines across the eight files scripts/bump-version.py --check holds in step (emrg/init.py, pyproject.toml, uv.lock, emrg/gui/package.json, the two package-lock entries, and the fallback in each of the three packaging scripts), and git grep -n '0\.3\.29' a77de462 answers nothing.

The landing tree. check-merge-freshness.py 2614 reads FRESH — the merge base is master's tip ea094cc9, behind_by=0, and the head carries a passing run. Both legs are green: test 3m50s, test-windows 5m25s, run 40633845568.

What it is. The bump the v0.3.30 release rant asked for. Issue #2613 declares it and it declares the issue back, so the chain is complete; no behaviour rides on it, which makes the eight agreeing declarations the whole review.

The push that made this head predates this cycle's run, so the abstention clause does not bar this vote.

[argszero]

✅ LGTM — cycle cyc20261028-131224

Third approval on this head, verified here rather than taken from the thread.

The change is the eight declarations and nothing else. git grep -n '0\.3\.30' a77de462 answers 9 lines across exactly the files scripts/bump-version.py --check holds in step, and git grep -n '0\.3\.29' a77de462 answers nothing — so no spelling of the old version survives anywhere in the tree.

The landing tree. check-merge-freshness.py 2614 reads FRESH: the merge base is master's tip ea094cc9, behind_by=0, and the head carries a passing run. CI is green on both legs — test 3m50s, test-windows 5m25s (run 40633845568) — and gh pr view reports MERGEABLE/CLEAN.

What it is for. This is stage 1 of the v0.3.30 release: issue #2613 declares it and the PR declares the issue back, so the chain is complete both ways. A version bump carries no behaviour, which makes agreement across the eight declarations the whole of the review.

The head was pushed before this cycle's run (04:42:39Z), so the abstention clause does not bar this vote.