From d41c4c53d5f57374c3a69ed43f15be1d62b81076 Mon Sep 17 00:00:00 2001 From: Stefano Guerrini Date: Thu, 15 Oct 2026 10:54:36 +0200 Subject: [PATCH] docs(release): say it more simply --- DEVELOPMENT.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 86396b3..e06c5b6 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -151,9 +151,9 @@ To publish an existing tag again, run the Release workflow by hand from ### If the checks fail after the release PR is merged -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 +The release PR runs CI like any other PR. After you merge it, the release +run checks the code again before it tags and publishes. If that check +fails, `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: