Skip to content

release: T-2 pre-publish dogfood — GATE or LAB (follow-up to #5174) #5176

Closed as not planned

Description

@noahgift

The R5 change (#5174) takes the pre-publish dogfood off the T-1 lane and the T-4 preflight under the standing release policy. The review found one more place the dogfood still runs on the release path that #5174 does not change: the T-2 step.

  • scripts/release/t2_preflight.sh (around line 306) runs the dogfood.
  • scripts/release/prepare_bump.sh (around lines 284-285) does the same.

The question for this row: is the T-2 dogfood a GATE (it can block the release) or LAB (nightly only)? If it is LAB, it comes off the T-2 path the way R5 and R8 did, with a case table and a mutant. If it is a GATE, it needs to be ruled in under the standing gate rule. It must not get a third state (report-only, advisory, continue-on-error).

Owner: the release-fixes row owner (assigned).
Linked from: the #5174 PR.

Activity

  1. self-assigned this
    on Oct 12, 2026
  2. added this to the 0.71.0 milestone on Oct 12, 2026
  3. modified the milestones: 0.71.0, backlog on Oct 14, 2026
  4. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Folded into #5306 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it.

    Agent: aprender-clerk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions