From 0226e64d58b7e8a922df99a5a538eeb85b86f835 Mon Sep 17 00:00:00 2001 From: Wagner Costa Date: Fri, 28 Aug 2026 21:17:47 -0300 Subject: [PATCH] docs: Explain the admin merge of release-please PRs and the App-token fix --- docs/runbooks/release.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/runbooks/release.md b/docs/runbooks/release.md index bb63da7..8c06eca 100644 --- a/docs/runbooks/release.md +++ b/docs/runbooks/release.md @@ -41,7 +41,12 @@ embedded AskNews skill. It must not contain credentials, `.env` files, tests, or ## Cut a release -Merge the open Release PR (title `chore(main): release X.Y.Z`). The workflow then: +Merge the open Release PR (title `chore(main): release X.Y.Z`). Note: the Release PR is opened with +`GITHUB_TOKEN`, and GitHub does not run `pull_request` workflows for such PRs, so CI never reports on +it and the `main` ruleset blocks a normal merge — merge it as an admin (`gh pr merge N --squash --admin`). +The commits in it already passed CI on their own PRs. To remove this step, give release-please an +org GitHub App token (`actions/create-github-app-token` → `token:` input); App-created PRs trigger CI +normally. The workflow then: 1. creates the tag and GitHub Release with the changelog notes; 2. installs dependencies and bundles `dist/` from the committed OpenAPI snapshot;