Skip to content

[release/0.11.0] ci(release): blobless full-history checkout and 20-minute budget for the stable gate - #29322

Closed
CrysisDeu wants to merge 1 commit into
release/0.11.0from
crew/build-watcher/stable-gate-checkout-0.11
Closed

CrysisDeu wants to merge 1 commit into
release/0.11.0from
crew/build-watcher/stable-gate-checkout-0.11

Conversation

@CrysisDeu

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: The v0.11.2 stable release run on release/0.11.0 gets past the Stable publication gate instead of being cancelled inside its checkout.

Backport of #29301 (gate part only) to release/0.11.0. On this branch the gate runs on the CodeBuild fleet for tag pushes, with fetch-depth: 0 and a 10-minute budget. Every failed v0.11.2 gate attempt in run 41703229734 ran on CodeBuild (jobs 126151838848 and 126179898554, labels codebuild-kirocrew-gha-linux-41703229734-1 / -2) and was cancelled at 10m inside actions/checkout.

Why it matters

The stable tag v0.11.2 lives on this branch, so its release run uses this branch's workflow. Until the gate fits its budget, v0.11.2 cannot publish.

Not a goal

What changed (motivation → approach → change)

Symptom: gate cancelled at 10m inside actions/checkout. Root cause: a full clone (every blob of every commit) is slower than the budget on the CodeBuild fleet. The gate needs every commit and tag and the working tree at the tagged commit, but never reads older blobs.

Change in .github/workflows/release.yml stable-gate (hand-applied; runs-on differs from main):

  • filter: blob:none on the checkout, keeping fetch-depth: 0.
  • timeout-minutes: 10 → 20 as headroom.

Backwards compatibility

Compatible: the gate reads the same refs and files; only the clone shape and the budget change.

Removes nothing: the job keeps full commit and tag history and every check it ran.

Tests

  • test/test_stable_release_gate.py::test_gate_full_history_checkout_is_blobless_and_has_headroom (new): pins filter: blob:none on the gate checkout and timeout-minutes >= 20. test_gate_checks_out_full_history still pins fetch-depth: 0.

Proof: not provable -- docs or config only

Manual verification

Required after merge: rerun the v0.11.2 release run; the Stable publication gate should finish well under 20 minutes.

Related Issues

N/A — backport of #29301.

Sibling sweep

Swept: grep -n "fetch-depth: 0" -B20 .github/workflows/*.yml on release/0.11.0 for jobs on the CodeBuild fleet with timeout-minutes of 10 or less
Sibling: .github/workflows/release.yml -- changed here
Sibling: .github/workflows/internal-content-scan.yml -- not affected -- runs on ubuntu-latest on this branch

Pattern harvest

Not generalizable: main already ratchets this class in test/test_workflow_bounded_checkout.py; this is a backport of that fix to a release branch.

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 gate

The stable publication gate needs every commit and tag, but on the
CodeBuild fleet a full fetch-depth: 0 clone takes 8.6-10+ minutes and
the 10-minute job timeout cancels the gate inside the checkout step.

Add filter: blob:none to the checkout (commits and tags all arrive, the
working tree is still populated at the tagged commit) and raise
timeout-minutes to 20 as headroom. A new test pins the filter and the
budget.
@CrysisDeu
CrysisDeu requested review from a team and KiroCrewCaptain as code owners November 3, 2026 21:04
@CrysisDeu
CrysisDeu requested review from chenmingwei23 and removed request for a team November 3, 2026 21:04
@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

UX Review (Opus 5.5) — ⏭️ skipped

Revision 10381692d67d7a85d0aa6a563144a9218b1d6aaf 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

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 10381692d67d7a85d0aa6a563144a9218b1d6aaf — 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

The blobless checkout targets the measured cause, a full clone that overruns the budget on CodeBuild. The timeout bump is reversible headroom.

Notes

  • Item 2 — inherited: the comment "can take most of ten minutes even with the blobless filter" has no measurement behind it. Raising 10 to 20 could hide a slow clone that the filter alone would otherwise show. Subtraction: once the first blobless run's checkout time is known, cut timeout-minutes back toward 10.

What this change ships

Inventory (3 items) — 2 justified

Intent: let the v0.11.2 stable release get past its publication gate instead of being cancelled during checkout. This is a FIX.

  1. The gate checkout clones full history without blobs of older commits (filter: blob:none). The gate step never runs git show, git diff or cat-file (0 matches in release.yml), so it never needs those blobs. — justified
  2. The gate's time budget goes from 10 to 20 minutes. — inherited, headroom not measured
  3. A test pins the blobless filter and a budget of at least 20 minutes. — justified

[FIRST-PRINCIPLES-REVIEWED] 1038169

Description read

[DESCRIPTION-READ] 9346a6d3405181289590ac955c23165cfd20da52b6edd483831b48b3c7bbe97c

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.

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

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

Design-Verdict: PASS

Nothing blocks: the gate only runs git rev-list on tags and reads CHANGELOG.md from the working tree. A blobless full-history clone serves both without fetching older blobs.

[DESIGN-REVIEWED] 1038169

Description read

[DESCRIPTION-READ] 4552758b997ba800315a21f13dc759295713491c0022b53fa77ca3587a1e8c0b

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

Opus 5.5 Review — ✅ no blocking findings

Reviewed 10381692d67d7a85d0aa6a563144a9218b1d6aaf — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 1038169

Verdict parsed from the review's SHA-scoped output markers for commit 10381692d67d7a85d0aa6a563144a9218b1d6aaf.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 10381692d67d7a85d0aa6a563144a9218b1d6aaf 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 10381692d67d7a85d0aa6a563144a9218b1d6aaf and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 1038169

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

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 3, 2026
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Superseded by #29325.

@CrysisDeu CrysisDeu closed this Nov 3, 2026
@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention 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