docs(changelog): document the v0.69.2 drift - #3592
Merged
Merged
Conversation
…ase CI wait `/gpk` squash-merges onto whatever `main` tip exists at merge time, so everything that lands during the release PR's CI wait ships in the release undocumented. Eleven commits did, and most are user-facing — three of them data-loss fixes. Also corrects the required-status-check list in `.github/CLAUDE.md`, which named three of the four; `fast-checks` is required too.
worktrunk-bot
approved these changes
Jul 25, 2026
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
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.
Eleven commits landed on
mainwhile #3590 sat in CI, so they ship in v0.69.2 with no changelog entry. Most are user-facing, and three are data-loss fixes — exactly the drift the release skill's step-12 check exists to catch. The tag is held until this lands.Entries added, most-impactful first:
conf.d/wt.fishdeleted outright byinstall's legacy cleanup. Plus forge detection moving fromhost.contains("github")to label-wise matching.wt step rebase&wt step pushon the docs site #3578 — despite itsdocs(step):subject this carries three behavior fixes, includingwt step pushsucceeding mid-rebase and moving the target branch onto a half-replayed history.wt step relocate --commit, andwt mergerefuses in its own name.Not documented, per convention: #3574 (doc comments only, no runtime or docs-site surface) and the three dependency bumps.
Also corrects
.github/CLAUDE.md, which lists three required status checks; there are four —fast-checksis required too, confirmed against the branch-protection API.Entries verified against the diffs by subagent. Two corrections came back and are folded in: the #3589 entry originally promised "two of them deleted" and described only one, and the #3578 entry mis-quoted the success line as
✓ Pushed to mainwhen it carries a commit count.