From 6d8440fa8f203db5c6b67049dac353102046af5c Mon Sep 17 00:00:00 2001 From: Shai Shmuel Date: Mon, 2 Nov 2026 19:06:52 +0200 Subject: [PATCH 1/2] docs(release): name the full-queue startup failure in recovery When an authoring run waits for its release-automation approval, later push runs queue behind it in the queue: max concurrency group. After 100 pending runs GitHub rejects every new Release run at startup with zero jobs and reports a likely workflow file issue, which points the investigation at the wrong place. Say so in the authoring recovery section and point at the existing cleanup. Co-Authored-By: Claude Opus 5.5 --- RELEASE.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/RELEASE.md b/RELEASE.md index fb14bc56a..1bb8a1f45 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -330,6 +330,12 @@ its source and workflow, while GitHub still permits the rerun; do not replay the obsolete backlog. Verify the generated PR's source ancestry after refresh, too: the approved run's revision does not freeze release-please's reads of `main`. +An authoring run left waiting for approval holds the release concurrency group, +so every later push queues behind it. Once 100 runs are pending, GitHub rejects +each new `Release` run at startup with zero jobs and reports that it likely +failed because of a workflow file issue. Before debugging the workflow file, +look for a `Release` run in the `waiting` state and apply the cleanup above. + ### Artifact publication Retain release build artifacts for at least 30 days. Normal recovery reruns From e00abbcf172d3a4a435a508057d941c962cba32c Mon Sep 17 00:00:00 2001 From: Shai Shmuel Date: Tue, 3 Nov 2026 11:26:25 +0200 Subject: [PATCH 2/2] docs(release): describe the full queue before its startup symptom Co-Authored-By: Claude Opus 5.5 --- RELEASE.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 1bb8a1f45..9e22d8626 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -331,10 +331,11 @@ obsolete backlog. Verify the generated PR's source ancestry after refresh, too: the approved run's revision does not freeze release-please's reads of `main`. An authoring run left waiting for approval holds the release concurrency group, -so every later push queues behind it. Once 100 runs are pending, GitHub rejects -each new `Release` run at startup with zero jobs and reports that it likely -failed because of a workflow file issue. Before debugging the workflow file, -look for a `Release` run in the `waiting` state and apply the cleanup above. +so every later push queues behind it. Once 100 runs are pending, the queue is +full and GitHub does not admit further `Release` runs. Each one appears as a +failed run with zero jobs, and GitHub reports that it likely failed because of a +workflow file issue. Before debugging the workflow file, look for a `Release` +run in the `waiting` state and apply the cleanup above. ### Artifact publication