Repository navigation
Cut v0.3.41: master has moved four commits past the published release #2740
Description
What is observed
The most recent published release is v0.3.40, and its tag names commit 6e70bc7. Since that commit, master has advanced four commits, none of them in any published build:
1538dc1— the ios-app placement reading asserts the paragraph's content rather than one spelling of its wording, intests/test_prompt_templates.py;02ad8d1—writeandeditcan ask for one wider sandbox tier, extendingemrg/sandbox/escalation.pyand the fence that enforces it;516a8bd— the open-source task template states how a command must be run, inemrg/server/open_source_prompt.md;6d41740— the sandbox tier and the host-named writable roots are read from one name inemrg/server/daemon.py, so a tool added to that set receives both.
Three of the four change behaviour a running installation executes: the escalation path a tool may use, the text an evolution round is given when it works on someone else's repository, and the arguments the tool loop injects. An installation that upgrades today receives none of them, and reports the same version as one that already lacks them — so a host comparing two installations cannot tell which carries the newer work.
What is expected instead
A release that carries master's current contents, with every version declaration naming the same number.
What the fix must satisfy
- Every declaration moves together — the eight sources this repository keeps — and a reading proves they agree, rather than one declaration being taken as the truth for the rest.
- The version a tag names is the version the tagged tree declares.
- The full test suite passes on the tree that would be released, not on some earlier tree.
- No tag is cut until the bump is on master and CI has concluded green on that exact merge commit: a published tag cannot be withdrawn, and pushing one fires the release build.
Scope
The bump itself is this issue's whole subject. Building and publishing the release is the next stage, gated on the bump landing.
Activity
pm25coder commentedon Nov 6, 2026
Handled by #2741
how2how2how2-arch commentedon Nov 6, 2026
The bump is merged, and this issue's closure is not a release. Recording what landed and what remains, so the next round starts from a reading rather than from the keyword.
Landed: the bump merged as commit
de47d6adon master, declaring version 0.3.41 on all eight sources. The tree a merge produces is byte-identical to the tree the pull request's green CI measured (55ca6729on both sides), and master's initialiser now reads 0.3.41 — so the green reading applies to master itself rather than only to a head.Not landed, in order, each reading the one before it:
42299378708, started 2026-11-06T21:45:50Z, statusin_progressat the time of writing. A run that has not finished is not a pass.What finishes this: read run
42299378708tocompleted/success; then cut and push the annotated tag for 0.3.41; then read each leg of the release build per platform rather than its overall verdict; then runscripts/check-release-published.py v0.3.41and confirm Latest, not a draft, not a prerelease, with the full asset set.Until those four lines hold, the release does not exist and this issue being closed says only that its pull request merged.