You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(release): name the full-queue startup failure in recovery - #882
Every Release run since 2026-10-26 22:47 UTC fails at startup with zero jobs, and GitHub says it "likely failed because of a workflow file issue". The workflow files are fine. The release concurrency queue is full.
Run 38540932484 (push of 44b51dc, 2026-10-14) has its release-please job waiting for approval on the release-automation environment. It holds the public-release-main concurrency group (.github/workflows/release.yml:27-30: queue: max, cancel-in-progress: false).
Exactly 100 later push runs are pending behind it, from 2026-10-14 to 40408909263 (7a86c3a, 2026-10-26 21:59).
This PR changes no workflow behavior. It adds the symptom to the release-PR authoring recovery section of RELEASE.md, so the next person goes to the documented cleanup instead of debugging the workflow file.
Unblocking the release (maintainer action, not part of this PR)
Follow the existing "Release-PR authoring" recovery in RELEASE.md:
Cancel the obsolete pending push runs. Keep only the one you intend to approve. The newest pending run, 40408909263, runs release.yml and release-please inputs that are identical to current main. Alternatively, cancel all of them and approve the run from the next push to main.
Then cancel the old waiting run 38540932484. If it is cancelled first, the oldest pending run starts next.
Approve the retained run's release-automation job, then review the release PR it opens as usual.
Test plan
python3 -m tools.ci.check_release_contract
mise run test -- tools/ci/tests/test_release_contract.py (94 passed)
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 <noreply@anthropic.com>
No actionable comments were generated in the recent review.
Walkthrough
RELEASE.md explains how an authoring run waiting for approval holds the release concurrency group and causes later pushes to queue. It describes the failure that occurs when 100 runs are pending and directs maintainers to check for a waiting Release run before debugging the workflow file.
Changes: Release documentation
Layer / File(s)
Summary
Explain the Release run queue condition RELEASE.md
The guidance describes the effect of an authoring run waiting for approval. It directs maintainers to check for a waiting Release run and apply the preceding cleanup before investigating the workflow file.
Suggested reviewers:mamayer19
Merge Risk: Minimal · up to e00ab
The release recovery guidance is mergeable; no actionable issue remains.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly and concisely identifies the documentation change: naming the full-queue startup failure in release recovery guidance.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Tip
🎯 Customize your risk assessments
Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.
✅ Automatic approvals, with your rules
Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.
CodeRabbit Verify
Run CodeRabbit Verify to test the changes in this pull request.
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Team
Run ID: cdd31d67-0e32-45e0-81f7-33885de0ad4f
Commits
Reviewing files that changed from the base of the PR and between 6d8440f and e00abbc.
Files selected for processing: 1
RELEASE.md
Files skipped from review as they are similar to previous changes: 1
RELEASE.md
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Summary
Every
Releaserun since 2026-10-26 22:47 UTC fails at startup with zero jobs, and GitHub says it "likely failed because of a workflow file issue". The workflow files are fine. The release concurrency queue is full.release-pleasejob waiting for approval on therelease-automationenvironment. It holds thepublic-release-mainconcurrency group (.github/workflows/release.yml:27-30:queue: max,cancel-in-progress: false).pendingbehind it, from 2026-10-14 to 40408909263 (7a86c3a, 2026-10-26 21:59).maxallows "up to 100 jobs or workflow runs" to be pending, and that when the queue is full "any additional jobs or workflow runs are canceled". The 101st run, fbc6055 (ci: run the CUDA 13 and candidate image builds when saved bundle locks change #857), was the first one rejected at startup. Every run since has been rejected the same way.release.ymland the ten reusable workflows it calls are byte-identical at 7a86c3a (last accepted run) and fbc6055 (first rejected run). The run'sreferenced_workflowsdoes not include any file ci: run the CUDA 13 and candidate image builds when saved bundle locks change #857 changed.actionlintreports only the knownconcurrency.queueschema gap, whichtools/ci/check_release_contract.pyalready exempts.This PR changes no workflow behavior. It adds the symptom to the release-PR authoring recovery section of
RELEASE.md, so the next person goes to the documented cleanup instead of debugging the workflow file.Unblocking the release (maintainer action, not part of this PR)
Follow the existing "Release-PR authoring" recovery in
RELEASE.md:release.ymland release-please inputs that are identical to currentmain. Alternatively, cancel all of them and approve the run from the next push tomain.release-automationjob, then review the release PR it opens as usual.Test plan
python3 -m tools.ci.check_release_contractmise run test -- tools/ci/tests/test_release_contract.py(94 passed)🤖 Generated with Claude Code
Summary by CodeRabbit