Skip to content

docs(release): require an up-to-date branch before a squash merge #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kvlonge merged 1 commit into from
Nov 2, 2026
Merged

docs(release): require an up-to-date branch before a squash merge #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,12 @@ run that leaves the release pull request unchanged does not repair it. To recove
release pull request, then merge the next up-to-date pull request; Release Please opens a fresh
release pull request from the verified tree.

A squash merge of a branch that is behind `main` breaks the release the same way, even when it
applies cleanly: the merged tree is not the one Verify checked. Update the branch and let Verify
finish on the new head before merging. When the recovery pull request touches only light paths,
such as this file, also run Verify by `workflow_dispatch` on its branch so the release base gets
every suite, not only the light checks.

`main` was rewritten after 0.1.0 to drop tool attribution trailers, with every tree unchanged, so
the `v0.1.0` tag points at the pre-rewrite commit and is not an ancestor of `main`.
`last-release-sha` in `release-please-config.json` names the rewritten 0.1.0 release commit, so
Expand Down
Loading