Skip to content

ci: give the 0.11 stable gate a blobless checkout and 20 minutes - #29325

Merged
buluoray merged 1 commit into
release/0.11.0from
crew/slack/0.11-stable-gate-timeout
Nov 3, 2026
Merged

buluoray merged 1 commit into
release/0.11.0from
crew/slack/0.11-stable-gate-timeout

Conversation

@buluoray

@buluoray buluoray commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Let the v0.11.2 stable release pass its publication gate by giving the gate's checkout on release/0.11.0 a blobless fetch and 20 minutes, as #29301 does on main.

The stable-gate job checks out full history (fetch-depth: 0) under timeout-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

What changed (motivation → approach → change)

git cherry-pick -x of 4e44f733a5 (#29301), limited to .github/workflows/release.yml. It conflicted only because release/0.11.0 runs this job on a different runs-on line; the two hunks below are main's text, word for word:

  • stable-gate: timeout-minutes: 10 -> 20, with main's two-line comment.
  • stable-gate checkout: filter: blob:none after fetch-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.md read 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

  • The 28 test files that read 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.yml part of #29301.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.

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>
@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners November 3, 2026 21:24
@buluoray
buluoray requested review from bolichen97 and removed request for a team November 3, 2026 21:24
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 3, 2026
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 252547a6aac5b1d670af1e012cf5b4c985a73841 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks. The gate only reads commit and tag objects (git rev-list) plus the checked-out CHANGELOG.md, and a blobless clone keeps both, so what the gate checks stays the same.

Notes

  • The description has two ## Backwards compatibility lines ("Compatible: …" and "Removes nothing: …"). Keep just the single Removes nothing: line.

[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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 252547a6aac5b1d670af1e012cf5b4c985a73841 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 252547a6aac5b1d670af1e012cf5b4c985a73841 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 252547a

Verdict parsed from the review's SHA-scoped output markers for commit 252547a6aac5b1d670af1e012cf5b4c985a73841.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 252547a6aac5b1d670af1e012cf5b4c985a73841 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 252547a6aac5b1d670af1e012cf5b4c985a73841 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 252547a

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 252547a6aac5b1d670af1e012cf5b4c985a73841 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 252547a6aac5b1d670af1e012cf5b4c985a73841 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

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 ships

Inventory (2 items) — 2 justified

Intent: let the v0.11.2 stable release get past its publication gate on release/0.11.0. This is a FIX.

  1. The stable gate job now has 20 minutes instead of 10 before it times out — justified
  2. The stable gate's full-history checkout no longer downloads file contents of older commits — justified

[FIRST-PRINCIPLES-REVIEWED] 252547a

Description read

[DESCRIPTION-READ] 8c76d05e5fe0cc1d249a94cfb8cdeb85f25d337c034a4c43a84c68cf45cd328f

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@buluoray
buluoray merged commit 443d8d0 into release/0.11.0 Nov 3, 2026
14 of 22 checks passed
@buluoray
buluoray deleted the crew/slack/0.11-stable-gate-timeout branch November 3, 2026 21:41
@github-actions github-actions Bot removed the readiness: checking Automated validation is still running label Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant