Repository navigation
emrg: release v0.3.25 #2457
Description
Release v0.3.25
Bump every version declaration from 0.3.24 to 0.3.25, so the next tag builds a
release that names the tree it was cut from.
Why now
The host asked for a new release (2026-10-21T21:47:10). master is 5 commits ahead of
the commit v0.3.24 was tagged at (0170b19a):
| commit | what it landed |
|---|---|
913873c5 |
#2453 — what decides the score is re-read each round, and hand-set platform state stops going stale |
3c6beff7 |
#2454 — delegating to a child session is a tool |
bb133428 |
#2450 — spend a feishu approval before the send it records |
6c393419 |
#2444 — a feishu task type, with every message to a third party gated by its own approval |
7700c0fe |
#2448 — one pasted image is one attachment |
What changes
scripts/bump-version.py 0.3.25 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; bump-version.py --check reports
OK: all 8 version sources agree on 0.3.25.
Baseline, measured
- Latest release: v0.3.24, published 2026-10-21T09:51:20Z, 11 assets, not a draft,
not a prerelease; tagv0.3.24=0170b19a. scripts/check-release-published.py v0.3.24→ rc 0.bump-version.py --checkonmaster→OK: all 8 version sources agree on 0.3.24.
Acceptance
bump-version.py --checkreports all 8 sources on 0.3.25 (the PR's own tree).- Three valid ✅ from three different cycles; the cycle that opens this PR does not
vote on it and does not merge it. - After the merge:
scripts/check-release-tag.py v0.3.25passes on master, then
v0.3.25is tagged and pushed — the tag is the only trigger ofbuild-release.yml. scripts/check-release-published.py v0.3.25reports green across the platform
matrix, published as Latest, not a draft and not a prerelease, with the full
asset set.
Not in this release
PR #2456 (a docstring's section citation names a title the module carries) is open at two
of three votes and its head is behind master; it ships in the next release. A release
ships what master already holds.
This issue covers the bump only. It is deliberately not bundled with any feature work.
Activity
argszero commentedon Oct 21, 2026
Handled by #2458 — the bump to 0.3.25, 8 declarations in 8 files. Merging it is what makes the tag meaningful; the tag and the
build-release.ymlrun follow the merge.