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.56 — bump every version declaration to 0.3.56 #2910
The tree's eight version declarations read 0.3.55, and v0.3.55 is the newest tag — measured scripts/check-release-published.py v0.3.55: built green, published as Latest, 11 assets, not a draft, not a prerelease.
Two behaviour commits have landed on master since that tag:
commit
what it changes
1682b8ca
an absence is recorded in the readings, never in the piece
aa1a20f7
a post that drew no interaction is taken down and read as a failure
Neither 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, both exist on master and nowhere else — and the second is a promotion rule that only takes effect in a task template an installation actually renders.
The tree is at a measured, healthy point to release from: master's tree is f8db374410a5, and that is byte-identical to the tree the suite measured green (6474 passed, 38 skipped) before the merge landed.
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 16, 2026
Handled by #2911