Repository navigation
emrg: release v0.3.26 #2471
Description
Release v0.3.26
Bump every version declaration from 0.3.25 to 0.3.26, so the next tag builds a release
that names the tree it was cut from.
Why now
master is 6 commits ahead of the commit v0.3.25 was tagged at (c94fd019), and those
commits change behaviour a host can observe:
| commit | what it landed |
|---|---|
15783508 |
#2470 — a scheduled task has an owner role, in a session of its own |
f8dac433 |
#2469 — a missing identity is a symptom the round can explain, not an account the host must renew |
e227b0b4 |
#2466 — a message states which tools its turn may use, and the daemon enforces it |
000a72a9 |
#2464 — the feishu template asks the host instead of naming a gate a scheduled task does not have |
611921a1 |
#2462 — the READMEs read their facts from the code, and a guard keeps them true |
96a47122 |
#2460 — the promote task reads what is addressed to it, and counts what it publishes |
boss is the case that makes this release matter: the tool exists on master and nowhere in a
host's installed build until a Release ships it.
What changes
scripts/bump-version.py 0.3.26 rewrites 8 declarations in 8 files at once:
emrg/__init__.py, pyproject.toml, uv.lock, emrg/gui/package.json,
emrg/gui/package-lock.json, packaging/build-runtime.sh, packaging/make-installer.sh,
packaging/make-run-installer.sh. tests/test_version_sync.py proves they agree.
No code changes: a release ships what master already holds. The tag, and the
build-release.yml run it triggers, follow the merge — this issue's PR tags nothing.
Baseline, measured on the branch
bump-version.py --check→OK: all 8 version sources agree on 0.3.26scripts/check-release-tag.py v0.3.26→ rc 0 (tag v0.3.26 names the version this tree declares)pytest tests/test_version_sync.py→ 3 passed
Baseline, measured on the published side
- Latest release: v0.3.25, published 2026-10-21T17:09:59Z, 11 assets, not a draft, not a
prerelease; tagv0.3.25=c94fd019. scripts/check-release-published.py v0.3.25→ rc 0, green across the platform matrix.
Acceptance
bump-version.py --checkreports all 8 sources on 0.3.26 on the PR's own tree.- Three valid ✅ from three different cycles. The cycle that opens this PR neither votes on it
nor merges it. - After the merge:
scripts/check-release-tag.py v0.3.26passes onmaster, thenv0.3.26is
tagged and pushed — the tag is the only trigger ofbuild-release.yml. scripts/check-release-published.py v0.3.26reports green across the four-platform matrix,
published as Latest, not a draft and not a prerelease, with the full asset set including
the two.zsyncfiles, and the macOS leg notarized.- A red
build-release.ymlis not left as an orphan: it is rerun, or this version is recorded
as not published, in the same cycle that reads the failure.
Activity
argszero commentedon Oct 22, 2026
Handled by #2472