Development record
The v0.15.1 release review found at CHANGELOG.md:54-56,61: Four Fixed lines are written as fixes to behaviour no earlier release had. 'A status fetch reads an app's push ... no longer asked about again' (iss-2610161928560772) concerns `abcd status`, which did not exist at v0.15.0. The three cloud lines ('no longer reported as started', 'no longer reports a refused commit', and the author identity line) concern scripts/cloud, which `git ls-tree v0.15.0 -- scripts/cloud` shows did not exist then either. A reader infers the features shipped earlier. The 'no longer' wording also contradicts the section's own preamb…
The v0.15.1 release review found at CHANGELOG.md:54-56,61: Four Fixed lines are written as fixes to behaviour no earlier release had. 'A status fetch reads an app's push ... no longer asked about again' (iss-2610161928560772) concerns abcd status, which did not exist at v0.15.0. The three cloud lines ('no longer reported as started', 'no longer reports a refused commit', and the author identity line) concern scripts/cloud, which git ls-tree v0.15.0 -- scripts/cloud shows did not exist then either. A reader infers the features shipped earlier. The 'no longer' wording also contradicts the section's own preamb…
Grounds
- declined: The finding is true, but a released changelog section is not rewritten: CHANGELOG.md has one writer, the ship path, which only inserts a new section under an empty Unreleased (principles/one-writer-per-file.md), and the v0.15.1 GitHub release body does not come from the file, so a hand edit would move only main's copy of a section whose tag and archive cannot change. The cause, the composer wording a fix to a surface new since the anchor as a fix, is iss-2610172148157726, so later cuts do not repeat it.
Frontmatter
| id | iss-2610171626391435 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610171626391435-the-v0-15-1-release-review-found-at.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610161928560772When an app pushed the tip of a status branch, the forge's activity record never names that push, because the pusher check passes over app actors; so every status fetch asks the forge about that branch again and shows the line that the record does not yet name the tip.
- iss-2610172148157726The release changelog composer writes a fix to a surface that did not exist at the anchor tag as a Fixed line saying the behaviour 'no longer' happens, so a release's notes describe a fix to something no earlier release had. v0.15.1's section has such lines for abcd status and the cloud scripts, all new since v0.15.0, because each record carries impact: fix and nothing ties an entry's section to whether its surface existed at the anchor.