Repository navigation
Release v0.3.46 #2781
Description
What this release carries
The published release is v0.3.45, and its tag names the commit where that version was declared. Master has advanced five commits since, and none of them is in any published build:
- a per-cycle memory note may open on a short label, and the narration guard's length bound is measured rather than assumed;
- the switch path is exercised in both directions, so a state that flips back is caught rather than only a state that moves forward;
- a behaviour change moves the documents it invalidates, so a stale sentence cannot outlive the change that made it stale;
- the settings page can sign in to aitokenpool with a GitHub account;
- a project's own documents are read by authority when they contradict each other, and the pull request says which document was followed.
Three of the five change behaviour a running installation executes. 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 finishing this issue means
- Every version declaration this repository keeps agrees on
0.3.46:scripts/bump-version.py --checkanswersOK: all 8 version sources agree on 0.3.46, andtests/test_version_sync.pyproves the same thing from inside the suite rather than one declaration standing in for the rest. - That bump is on master with CI concluded green on that exact merge commit.
scripts/check-release-tag.py v0.3.46answers that the tag name resolves to the version the merged tree declares.- The annotated tag
v0.3.46is pushed. The tag is the only trigger ofbuild-release.yml; no other event signs or notarizes a build. scripts/check-release-published.py v0.3.46answers green across the platform matrix, published as Latest — not draft, not prerelease — with the full asset set.
Until the fifth reading answers, this release is a version string and not a release, and an installation that upgrades on the strength of the number alone receives nothing new.
Activity
how2how2how2-arch commentedon Nov 9, 2026
Handled by #2782
how2how2how2-arch commentedon Nov 9, 2026
Held open deliberately: the bump merge is not the release.
#2782merged as45680542on 2026-11-09T22:14:01Z, and its closing keyword closed this issue one second later — while nothing had been published. No tag exists on the remote, the release workflow has never run for this version, and the issue's own completion is the fifth of the steps it lists, not the first.Reopened to carry the four steps that remain. Each is a reading, and none is inferred from the merge:
45680542itself — not on the PR head (9a3eaf45), which is a different tree.scripts/check-release-tag.py v0.3.46on that merged tree: the tag name must resolve to the version this tree declares.v0.3.46. It is the only trigger of the release build; no other event signs or notarizes.scripts/check-release-published.py v0.3.46green across the platform matrix, published as Latest — not draft, not prerelease — with the full asset set.Until the fourth reading answers, this issue is not done, and an installation upgrading on the strength of the version string alone receives nothing new.
This is the same failure the issue-tracker cannot currently warn about: a merge is not an artifact. The row that should have said so is
#2780, whose fix is#2783.how2how2how2-arch commentedon Nov 9, 2026
Release finished, on the artifact's own reading rather than on a merge.
The fifth step this issue names is the one that settles it, and it now answers:
scripts/check-release-published.py v0.3.46→ exit 0:draft=False prerelease=False assets=11, and GitHub's Latest is this tag.42710810735,completed/success, on the tagged commit45680542— the same sha Test concluded green on, so the tag does not rest on a tree nobody tested.EMRG-0.3.46-aarch64.AppImageand its.zsync,linux-aarch64.run,linux-aarch64.tar.gz,linux-x86_64.run,linux-x86_64.tar.gz,macos-arm64.pkg,windows-x64.exe,windows-x64.zip,x86_64.AppImageand its.zsync.An installation upgrading now receives the five commits this version carries, which it could not before — that was the whole point of the bump.
Closing on that reading.