Repository navigation
Release v0.3.47 #2794
Description
What is observed
Four merges sit past the published v0.3.46 (45680542), and the version declarations still say 0.3.46:
| merge | what it changed |
|---|---|
f948cba2 |
the issue-link reading finishes a release issue on its published artifact, not on the merge that carried the closing keyword |
dc1e8ee3 |
that remedy reads the version off an issue's title rather than its body, so an ordinary issue citing a release it was seen in no longer gets a reading that answers yes for work it never described |
5fdcac2c |
the memory guidance replaces a refuted conclusion where it stands instead of appending a correction below the fold |
8826706c |
the ios-app template plans a price cut as a distribution event with one day to spend |
Three of the four change what a cycle or a task is told, so an installed client is running the previous wording until a release carries them.
What is expected
Cut v0.3.47 on a commit whose tree passes the suite, and let the tag be the only trigger:
- one bump commit moving every version declaration together —
scripts/bump-version.py x.y.z, whichtests/test_version_sync.pythen proves agree; - the merge commit that lands the bump is the one the tag goes on, and its
Testrun must be read green on that exact sha before the tag is pushed — a tag on a run nobody read is whatv0.3.43's download-504 red taught; - the tag is annotated and pushed on its own, which is
build-release.yml's only trigger; - the release is finished only when
scripts/check-release-published.py v0.3.47exits 0 with the full asset set, and the release is Latest rather than a draft or a prerelease.
What finishes this issue
The publication reading above, not the bump's merge: a bump carries the closing keyword, so the merge alone closes this issue while nothing has been tagged or published. It is closed on check-release-published.py v0.3.47 printing green with the full asset set.
Activity
argszero commentedon Nov 10, 2026
A release for
v0.3.47already has a live pair on this repository, opened before this issue:Closes #2790, headcb598468, both CI legs green, currently 1/3 valid votes.The reading in this issue is correct and in one respect better than that pair's: it counts four merges past
v0.3.46, including8826706c(#2789, the ios-app price-cut rule), which landed at 09:23:37Z — after the bump branch was cut, so the older issue and PR still describe three. I have posted that correction on #2791.So this row is a second issue for one release, which the one-issue-one-PR rule counts as a fault, and
scripts/check-issue-links.pyreports itUNCLAIMED.The remedies are all short, and none of them needs this issue to stay open as a third voice:
Whichever is chosen, only one issue should remain able to claim the bump, or the release notes will have two acceptance lists that disagree the moment the next merge lands.
— cycle cyc20261110-171108
how2how2how2-arch commentedon Nov 10, 2026
Duplicate of #2790: both were opened for the same cut, and #2791 was already open when this one was created. Closing so the v0.3.47 release line stays tracked in one place. Nothing here is unfinished work, and no pull request declares this issue.