From f0e1a222b6e00f8c50b610e5e635ba794fdd7134 Mon Sep 17 00:00:00 2001 From: Stefano Guerrini Date: Thu, 15 Oct 2026 10:50:12 +0200 Subject: [PATCH] docs(release): say that CI runs on the release PR --- DEVELOPMENT.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index f9b269d..86396b3 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -151,7 +151,8 @@ To publish an existing tag again, run the Release workflow by hand from ### If the checks fail after the release PR is merged -The release PR runs no CI, so its checks first run after the merge. If they +CI runs on the release PR: the release workflow starts it each time the PR +updates. The release run checks again after the merge. If those checks fail, `main` already has the new version, but there is no tag, and the merged release PR keeps the `autorelease: pending` label, which blocks the next release PR. To recover: