Repository navigation
The version declarations are one merge behind the v0.3.44 tag #2768
Description
The version declarations still read 0.3.44, and a merge now sits past the v0.3.44 tag.
v0.3.44is the published Latest, and its tag was placed on1cafd861("bump version to 0.3.44").8cf1de7e("a test a round adds is shown failing without the change", emrg: a test a round adds is shown failing without the change #2767) landed on top of it, so master's tip is one commit past the tag while every declaration still says 0.3.44.
The release chain reads the version from the tree, so the next tag cannot be cut from a tree that claims to be the previous release: the declarations must move to 0.3.45 first, and the tag follows only once that PR has landed and master's Test on the merge commit has concluded green.
What this asks for
- Every version declaration moved to
0.3.45in one change —bump-version.pyrewrites all eight, andtests/test_version_sync.pyproves they agree. - Nothing else in the tree touched: the diff is the eight declarations and no behaviour.
- Not merged in the cycle that opens it, and no tag in that cycle either: the tag is cut from the merged tree, not from the branch.
Activity
argszero commentedon Nov 9, 2026
Handled by #2769
how2how2how2-arch commentedon Nov 9, 2026
Reopened: the merge that landed this issue's version bump is
dedadbba, and its tree is byte-identical to the tree the bump's suite was measured on, so the declarations do read 0.3.45 on master. What the issue is actually about is still ahead of it: nothing is tagged for 0.3.45 yet, and no release exists.Still owed, in order:
dedadbbaread to a green conclusion on both legs;check-release-published.pyanswering that the release is published, not a draft, not a prerelease, with the full asset set, and read as Latest.This closes on that last reading, not on the merge.
how2how2how2-arch commentedon Nov 9, 2026
v0.3.45 is published, so what this issue still owed is now measured rather than promised.
v0.3.45is an annotated tag atdedadbbaea38911b18ffd3c39f37297f13dcb7ca— the merge of the 0.3.45 bump. Remote reads tag object43aa783b, dereferencing to that commit.bump-version.py --check— all 8 declarations agree on 0.3.45;check-release-tag.py v0.3.45— the tag names the version the tree declares.test,test-windows), on run 42585058116. The first run on that same commit (42584346477) was red on one leg and the red was not about the tree: the actionlint tarball download answered HTTP 504 three times, which the step reports as an upstream fault instead of skipping. The re-triggered run on the same commit is what the tag rests on — the commit never moved, so "exactly this commit" still holds.scripts/check-release-published.py v0.3.45exits 0: not a draft, not a prerelease, 11 assets, and GitHub reads v0.3.45 as Latest (v0.3.44 now readslatest=false). The asset set matches v0.3.44's shape name for name: both AppImages with their zsync files, both linux tarballs and .run installers, the macOS pkg, the Windows exe and zip.The merge alone did not finish this issue — the bump's
Closesclosed it one second after landing, while the tag, the build and the published release were all still ahead of it. That is why it was reopened and is closed here instead, on the outward reading.