PerishLab/plumb
1
0
Fork 0
Code Issues 11 Pull requests 22 Projects Releases Packages 1 Wiki Activity Actions

Give v0.26.0 back the beta it was actually generated by #353

Open
PerishFire wants to merge 1 commit from task/frozen-history-says-beta-4 into main
pull from: task/frozen-history-says-beta-4
merge into: PerishLab:main
Conversation 0 Commits 1 Files changed 2 +2 -2
PerishFire commented 2026-08-19 01:38:43 +00:00
Owner
Copy link

plumb release compile refused v0.27.0-beta.2:

plumb release: candidate mutates frozen changelog v0.26.0 while releasing v0.27.0

It is right on both counts.

The mutation is one line in each language, changing the beta that v0.26.0 records as its generator from v0.26.0-beta.4 to v0.26.0-beta.5. It landed during the v0.26.0 release itself, when a beta.5 was expected to be cut.

None was. The highest exact point on that line is beta.4, and the release was finished from it by hand. So the sentence has been naming a release point that never existed — in the immutable record of a shipped version — since the day it shipped.

Both halves of the rule apply: frozen changelog history is not a thing to correct, and this correction was false. The files are restored to what the v0.26.0 tag holds, which is also what happened.

Nothing caught it for a release because no release ran between then and now. That is the useful part: the gate is real, it fired the first time it could, and what it found was not a formatting slip but a claim about provenance that was wrong.

`plumb release compile` refused v0.27.0-beta.2: ``` plumb release: candidate mutates frozen changelog v0.26.0 while releasing v0.27.0 ``` **It is right on both counts.** The mutation is one line in each language, changing the beta that v0.26.0 records as its generator from `v0.26.0-beta.4` to `v0.26.0-beta.5`. It landed during the v0.26.0 release itself, when a beta.5 was expected to be cut. **None was.** The highest exact point on that line is beta.4, and the release was finished from it by hand. So the sentence has been naming a release point that never existed — in the immutable record of a shipped version — since the day it shipped. Both halves of the rule apply: frozen changelog history is not a thing to correct, and this correction was false. The files are restored to what the `v0.26.0` tag holds, which is also what happened. Nothing caught it for a release because **no release ran between then and now**. That is the useful part: the gate is real, it fired the first time it could, and what it found was not a formatting slip but a claim about provenance that was wrong.
Give v0.26.0 back the beta it was actually generated by
All checks were successful
guard / guard (pull_request) Successful in 2m50s
Details
976ee85a7d 
`plumb release compile` refused this release: the candidate mutates the frozen
changelog of v0.26.0 while releasing v0.27.0. It is right on both counts.

The mutation is one line in each language, changing the beta that v0.26.0
records as its generator from `v0.26.0-beta.4` to `v0.26.0-beta.5`. It landed
during the v0.26.0 release itself, when a beta.5 was expected to be cut. None
was: the highest exact point on that line is beta.4, and the release was
finished from it by hand. So the sentence has been naming a release point that
never existed, in the immutable record of a shipped version, since the day it
shipped.

Both halves of the rule apply. Frozen changelog history is not a thing to
correct, and this correction was false. The files are restored to what the
v0.26.0 tag holds, which is also what happened.

Nothing caught it for a release because no release ran between then and now.
That is the useful part: the gate is real, it fired the first time it could, and
what it found was not a formatting slip but a claim about provenance that was
wrong.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
All checks were successful
guard / guard (pull_request) Successful in 2m50s
Details
This pull request has changes conflicting with the target branch.
  • docs/CHANGELOG/v0.26.0/en/INDEX.md
  • docs/CHANGELOG/v0.26.0/zh/INDEX.md
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin task/frozen-history-says-beta-4:task/frozen-history-says-beta-4
git switch task/frozen-history-says-beta-4
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishLab/plumb!353
No description provided.