pgw#1323: attribute the silent release note to the wheel that shipped it - #934
Open
PaulFidika wants to merge 1 commit into
Open
pgw#1323: attribute the silent release note to the wheel that shipped it#934PaulFidika wants to merge 1 commit into
PaulFidika wants to merge 1 commit into
Conversation
…y shipped it pgw#1323's code shipped in 0.121.0 with no fragment, no consumed.tsv row and no mention in that section — a silent release note, verified four ways when it was found. Two cutters then tried the documented repair and backed it out, because `--version <older>` swept every pending fragment into the older section: 5 fragments for the 0.122.0 cutter, 16 for me on the 0.123.0 attempt. pgw#926 fixed the assembler, and this is the repair it makes safe. Run on fc25405's successor, it does exactly what docs/releasing.md always promised: pgw1323.md -> 0.121.0 (late; its code shipped in v0.121.0) 2 fragment(s) pending, not in 0.121.0: <- HELD, not swept pgw1346-b3a-families.md ... unshipped work cannot be dated into it pgw1355.md ... unshipped work cannot be dated into it Verified rather than assumed: exactly ONE `## 0.121.0` heading (the old bug prepended a duplicate), exactly one new ledger row `0.121.0 pgw1323`, the bullet inside the real section under the "*Attributed after the cut (pgw#1226)*" note, and `pyproject.toml` untouched — this is a repair, not a cut, and it bumps nothing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pgw#1323's code shipped in 0.121.0 with no fragment, no
consumed.tsvrow and no mention in that section. Two cutters tried the documented repair and backed it out, because--version <older>swept every pending fragment into the older section — 5 for the 0.122.0 cutter, 16 for me on the 0.123.0 attempt.pgw#926 fixed the assembler; this is the repair it makes safe:
Verified, not assumed: exactly one
## 0.121.0heading (the old bug prepended a duplicate), exactly one new ledger row0.121.0\tpgw1323, the bullet inside the real section under the "Attributed after the cut (pgw#1226)" note, andpyproject.tomluntouched — a repair, not a cut.