Repository navigation
Tie a changelog fix's prominence to its reach - #4295
Merged
Merged
Conversation
The 0.80.0 draft named every bug's conditions, joined with "and", as the release skill asked, yet still read as severe: each of fourteen fixes got its own bullet under a headline stating the consequence, and conditions in the body don't undo a headline a reader has already skimmed. The rule now puts the conditions in the headline, folds near-zero-interest fixes into one roll-up bullet, and the verifier template checks headlines read alone. evals/ gains the 0.80.0 research notes as a drafting case. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…t as its case Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…erity-instructions
worktrunk-bot
approved these changes
Sep 27, 2026
Merged
max-sixty
added a commit
that referenced
this pull request
Sep 27, 2026
Bumps 0.79.0 → 0.80.0 and adds the `## 0.80.0` changelog section, cut from `12efb5159`. The bump is minor because the library API breaks (see Verification). ## Verification - `cargo run -- hook pre-merge --yes` on the cut tip: 4985 passed. - `nightly.yaml` on `12efb5159`, all jobs green including feature-powerset: https://github.com/max-sixty/worktrunk/actions/runs/36338233859 - `cargo semver-checks check-release -p worktrunk` reports five major-level lints, the removals and signature changes listed in the Internal entry. - Changelog: repeated verification passes against source until one came back clean. Fixed headlines name the condition a bug needed rather than its worst case, and near-zero-reach fixes are folded into two roll-up bullets, per #4295. - Data-loss surface review over `v0.79.0..HEAD` with independent finders. The one real finding, a nested stale detached worktree read as the enclosing repo's rebase so `wt step prune` could unregister it, was fixed in #4302. The review also found a squash regression in the backup path, fixed in #4303. The remaining candidates were adjudicated acceptable and signed off: #4228 unregistering stale worktrees whose directory remains (files stay on disk; the branch is deleted only if integrated), #4206 leaving a detached `HEAD` on Ctrl-C during a slow commit hook, #4251 allowing `--no-squash` merges with untracked files, #4219 dropping `--no-hooks` from the skill example, and #4279's `docker stop` recipe. #4252 closes a submodule data-loss path. > _This was written by Claude Code on behalf of max-sixty_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
2 participants
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.
The 0.80.0 changelog draft followed the release skill's "Name the conditions a bug needed" rule to the letter — every Fixed entry named its conditions, joined with "and" — yet still read as severe. Each of fourteen fixes got its own bold bullet, and most headlines stated the consequence (
wt removeno longer deletes submodule changes hidden by config), so extreme corner cases such as a pre-remove hook corrupting the user config read as general breakage. Readers skim headlines; conditions in the body arrive too late. The drafter's own research had labelled most of these fixes "rare" or "near zero" reach, and three verifier passes came back clean because the template checked accuracy, length, and ranking only.The rule becomes "Match a fix's prominence to its reach": conditions go in the headline and the consequence in the body, and a fix of near-zero reader interest folds into a closing "Fixes for unusual setups" bullet instead of getting its own. It reuses the skill's existing definition of reader interest (reach combined with obligation), so a rare breaking change still keeps its own bullet. The verifier template gains a check that reads each headline alone.
evals/gains the 0.80.0 research notes and the first draft as a case. Pasting the old and new guidance with those notes, 3 runs each:The failed-squash fix, which anyone with a failing commit hook hits, kept its own top bullet in every drafting run.
🤖 Generated with Claude Code