Repository navigation
ci: give the 0.11 stable gate a blobless checkout and 20 minutes - #29325
Conversation
The stable publication gate's full-history checkout ran into its 10-minute limit on five attempts in a row of the v0.11.2 stable run, so the gate never reached its own checks. This takes only the release.yml stable-gate change of #29301: timeout-minutes 20 and filter: blob:none on that checkout. The rest of #29301 (internal-content-scan.yml and its tests) is not carried. (cherry picked from commit 4e44f73) Co-authored-by: Zezhen Xu <32421101+CrysisDeu@users.noreply.github.com>
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks. The gate only reads commit and tag objects ( Notes
[DESIGN-REVIEWED] 252547a Description read[DESCRIPTION-READ] 334d6def7d51d5724cf36ffc188bcb9d27616807a46132f47330869702150727 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing blocks. Both changes answer a failure the author measured: stable run 41703229734, whose checkout hit the time limit on all five attempts. What this change shipsInventory (2 items) — 2 justifiedIntent: let the v0.11.2 stable release get past its publication gate on
[FIRST-PRINCIPLES-REVIEWED] 252547a Description read[DESCRIPTION-READ] 8c76d05e5fe0cc1d249a94cfb8cdeb85f25d337c034a4c43a84c68cf45cd328f That sha256 names the PR description this verdict read. Recompute it with |
Problem / Motivation
Goal: Let the v0.11.2 stable release pass its publication gate by giving the gate's checkout on
release/0.11.0a blobless fetch and 20 minutes, as #29301 does onmain.The
stable-gatejob checks out full history (fetch-depth: 0) undertimeout-minutes: 10. On the v0.11.2 stable run (41703229734) that checkout hit the limit on attempts 1 to 5, so the gate's own check step never ran and nothing was published. The only two passes of this gate on the 0.11.2 line took 5m16s and 8m36s.Why it matters
Stable users stay on 0.11.1 until the gate can run. Rerunning has failed five times in a row, and removing 359 stale branches (1,678 to 1,320) did not change the result.
Not a goal
internal-content-scan.ymland the two test files stay as they are onrelease/0.11.0.What changed (motivation → approach → change)
git cherry-pick -xof4e44f733a5(#29301), limited to.github/workflows/release.yml. It conflicted only becauserelease/0.11.0runs this job on a differentruns-online; the two hunks below are main's text, word for word:stable-gate:timeout-minutes: 10->20, with main's two-line comment.stable-gatecheckout:filter: blob:noneafterfetch-depth: 0, with main's three-line comment.The gate still gets every commit and tag, and the working tree is checked out in full, so its tag lookup and
CHANGELOG.mdread are unchanged.Backwards compatibility
Compatible: only the gate job's time budget and fetch filter change.
Removes nothing: no step, check or key is removed.
Tests
Proof: not provable -- docs or config only
release.yml: 1571 passed, 3 skipped. The YAML parses.Manual verification
The next release run on this branch's merge commit shows the gate checkout's duration.
Related Issues
Part of the v0.11.2 release; ports the
release.ymlpart of #29301.Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.