Skip to content

docs(release): name the full-queue startup failure in recovery #882

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
ShaiShmuel merged 2 commits into from
Nov 3, 2026
Merged

docs(release): name the full-queue startup failure in recovery #882

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6d8440f
docs(release): name the full-queue startup failure in recovery
ShaiShmuel Nov 2, 2026
e00abbc
docs(release): describe the full queue before its startup symptom
ShaiShmuel Nov 3, 2026
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: 7 additions & 0 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -330,6 +330,13 @@ 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, 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

Retain release build artifacts for at least 30 days. Normal recovery reruns
Expand Down
Loading