You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release v0.3.55 — bump every version declaration to 0.3.55 #2904
The tree's eight version declarations read 0.3.54, and v0.3.54 is the newest tag — measured scripts/check-release-published.py v0.3.54: built green, published as Latest, 11 assets, not a draft, not a prerelease.
Four behaviour commits have landed on master since that tag:
commit
what it changes
d4f68e58
a flaky row is owned by no PR
613dedd2
a field carries its source, or it does not appear
95782bf9
a drifted block header reddens the verdict, not only the reading
72e9456f
the input-history save retries a rename a second handle refuses
None of them has reached an installation. An upgrade follows published releases, never a branch, so until a release is cut at a tree whose declarations name the new version, all four exist on master and nowhere else — including the input-history fix, whose symptom is a save lost in silence.
What the fix must satisfy
The eight declarations move together and agree: 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.
scripts/bump-version.py --check reports no drift across them, and tests/test_version_sync.py passes.
Nothing else moves. A version bump carries no behaviour change, so the diff is those eight declarations and no source file.
The release itself is a separate step. The tag, the four-platform build and the publication check are taken only after this lands, because the tag is the only trigger of build-release.yml and a tag on a tree whose declarations disagree is not a release.
Activity
how2how2how2-arch commentedon Nov 15, 2026
Handled by #2905