From a9078a3aa4bc25453d4e8948dde59d3acea2c22e Mon Sep 17 00:00:00 2001
From: Kevin Longe <273747162+kvlonge@users.noreply.github.com>
Date: Fri, 6 Nov 2026 01:48:17 +0000
Subject: [PATCH] docs(release): say that a maintainer merges the release pull
 request

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.
---
 .github/RELEASING.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/.github/RELEASING.md b/.github/RELEASING.md
index 69b0a964..196eace0 100644
--- a/.github/RELEASING.md
+++ b/.github/RELEASING.md
@@ -13,10 +13,11 @@ starts the trusted release workflow.
    release head SHA. It reuses `Verify` only after proving the release base tree matches
    the successfully verified head of that specific merged pull request. Trusted code from
    that base checks every owned manifest and lockfile version before and after lock refresh.
-4. Only after every trusted check passes, the workflow squash-merges the release pull
-   request and dispatches Release Please on `main` again.
-5. Release Please creates the GitHub `v0*` release. The workflow dispatches `publish.yml`
-   for that exact tag.
+4. Each trusted check reports its result as a commit status on the release head. Once those
+   statuses and the pull request's own required checks pass, a maintainer squash-merges the
+   release pull request. The workflow does not merge it.
+5. The merge to `main` runs Release Please again, which creates the GitHub `v0*` release. The
+   workflow dispatches `publish.yml` for that exact tag.
 6. Publish builds every supported native wheel plus both source distributions, validates
    the standalone CLI wheel tags, publishes through PyPI trusted publishing, and publishes
    `fensu-policy` through crates.io trusted publishing. The Rust analyzer is included in the