Skip to content

docs: Explain the admin merge of release-please PRs and the App-token fix #5

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
wagnercosta merged 1 commit into from
Aug 29, 2026
Merged

docs: Explain the admin merge of release-please PRs and the App-token fix #5

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
7 changes: 6 additions & 1 deletion docs/runbooks/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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;
Expand Down
Loading