Skip to content

docs(release): say that a maintainer merges the release pull request - #130

Merged
kvlonge merged 1 commit into
mainfrom
docs/release-merge-step
Nov 6, 2026
Merged

kvlonge merged 1 commit into
mainfrom
docs/release-merge-step

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Why

.github/RELEASING.md says the release workflow squash-merges the release pull request after its trusted checks pass. It does not: release-please.yml ends after posting the trusted checks as commit statuses, and release pull requests (#127, #129) are merged by a maintainer.

Changes

  • Steps 4 and 5 of the trusted release flow now say that a maintainer squash-merges the release pull request once the trusted statuses and the pull request's own required checks pass, and that the merge to main runs Release Please again to create the release and dispatch publish.yml.

Verification

  • Compared with .github/workflows/release-please.yml: the last step, "Run required release checks", posts statuses and has no merge.
  • The 0.29.2 release followed this order: chore(main): release 0.29.2 #129 merged by hand, Release Please on main created v0.29.2, then publish.yml was dispatched.

The release workflow posts its trusted checks as commit statuses and stops;
a maintainer squash-merges the release pull request, and the merge runs
Release Please again to tag and publish.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying fensu with  Cloudflare Pages  Cloudflare Pages

Latest commit: a9078a3
Status: ✅  Deploy successful!
Preview URL: https://c238c29a.fensu.pages.dev
Branch Preview URL: https://docs-release-merge-step.fensu.pages.dev

View logs

@kvlonge
kvlonge merged commit d4c25ba into main Nov 6, 2026
35 checks passed
@kvlonge
kvlonge deleted the docs/release-merge-step branch November 6, 2026 02:02
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.

1 participant