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

Write a changelog the size of the release #355

Open
PerishFire wants to merge 1 commit from task/a-changelog-the-size-of-the-release into main
pull from: task/a-changelog-the-size-of-the-release
merge into: PerishLab:main
Conversation 0 Commits 1 Files changed 4 +235 -448
PerishFire commented 2026-08-19 01:55:26 +00:00
Owner
Copy link

plumb release compile refused the seal:

changelog ./docs/CHANGELOG/v0.27.0 en has 313 lines, above diff budget 192 for 2282 units

The budget scales with what changed — (4 * scale(units)).clamp(120, 800) — and this changelog had stopped being a record of a release and become an essay about it.

The trim is not only shorter, it is more honest. Two sections described the same re-modelling: the point moving to the release family, and then the whole of the lock form following it. They were written at two moments of arriving at one conclusion, and a reader does not need the order I understood things in. They are one section now; the rest is the same content with the narration taken out.

en  313 → 192
zh  241 → 149
`plumb release compile` refused the seal: ``` changelog ./docs/CHANGELOG/v0.27.0 en has 313 lines, above diff budget 192 for 2282 units ``` The budget scales with what changed — `(4 * scale(units)).clamp(120, 800)` — and this changelog had stopped being a record of a release and become an essay about it. **The trim is not only shorter, it is more honest.** Two sections described the same re-modelling: the point moving to the release family, and then the whole of the lock form following it. They were written at two moments of arriving at one conclusion, and a reader does not need the order I understood things in. They are one section now; the rest is the same content with the narration taken out. ``` en 313 → 192 zh 241 → 149 ```
Write a changelog the size of the release
All checks were successful
guard / guard (pull_request) Successful in 3m4s
Details
211817a824 
`plumb release compile` refused the seal: the English changelog ran 313 lines
against a budget of 192 for a 2282-unit diff. The budget scales with what
changed, and this one had stopped being a record of a release and become an
essay about it.

The trim is not only shorter, it is more honest. Two sections described the same
re-modelling — the point moving to the release family, and then the whole of the
lock form following it — because they were written at two moments of arriving at
one conclusion. A reader does not need the order I understood things in. They
are one section now, and the rest is the same content with the narration taken
out.

Both languages are inside the budget, which is what a release is entitled to
say about itself at this size.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
All checks were successful
guard / guard (pull_request) Successful in 3m4s
Details
This pull request has changes conflicting with the target branch.
  • docs/CHANGELOG/v0.27.0/en/INDEX.md
  • docs/CHANGELOG/v0.27.0/en/MIGRATION.md
  • docs/CHANGELOG/v0.27.0/zh/INDEX.md
  • docs/CHANGELOG/v0.27.0/zh/MIGRATION.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/a-changelog-the-size-of-the-release:task/a-changelog-the-size-of-the-release
git switch task/a-changelog-the-size-of-the-release
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!355
No description provided.