Skip to content

docs(changelog): fold #3549 and #3539 into the 0.69.0 changelog - #3562

Merged
max-sixty merged 1 commit into
mainfrom
release
Jul 24, 2026
Merged

docs(changelog): fold #3549 and #3539 into the 0.69.0 changelog#3562
max-sixty merged 1 commit into
mainfrom
release

Conversation

@max-sixty

Copy link
Copy Markdown
Owner

docs(changelog): fold #3549 and #3539 into the 0.69.0 changelog

Both merged to main during the v0.69.0 release PR's CI window, so they
ship in 0.69.0 but weren't covered by the changelog:

#3320 also landed in the window but only touches the running-tend skill
(not shipped to users), so it gets no changelog entry.

This was written by Claude Code on behalf of max

Both merged to main during the v0.69.0 release PR's CI window, so they
ship in 0.69.0 but weren't covered by the changelog:

- #3549 fixes a data-corruption bug where `wt merge` / `wt step squash` /
  `wt step rebase` measured the span against a stale local target ref and
  folded already-upstream commits into the local default branch
  (fixes #3519, thanks @starlightromero for reporting).
- #3539 makes a signal-killed rebase exit as a clean interrupt (130/143)
  instead of a spurious merge conflict.

#3320 also landed in the window but only touches the running-tend skill
(not shipped to users), so it gets no changelog entry.

> _This was written by Claude Code on behalf of max_
@max-sixty
max-sixty merged commit c1c70a7 into main Jul 24, 2026
39 checks passed
@max-sixty
max-sixty deleted the release branch July 24, 2026 01:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

wt merge trusts stale local default-branch ref, can squash unrelated already-upstream commits into it

2 participants