From 128fb1a9d49c4b386d2cb60e80fb8b0e5bcdc936 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 24 Oct 2026 22:39:50 -0700 Subject: [PATCH 1/2] chore(quest): claim quest/m0/ci/release-gates.md Quest-Claim: 9d7abaead0eccb25 From f0de19ba0e5bab2233da4f3178878d8b7fa2774d Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sat, 24 Oct 2026 22:50:22 -0700 Subject: [PATCH 2/2] quest: wait on the release gate backport and ruleset Co-Authored-By: Claude Opus 5.5 --- quest/m0/ci/release-gates.md | 31 +++++++++++++++---------------- 1 file changed, 15 insertions(+), 16 deletions(-) diff --git a/quest/m0/ci/release-gates.md b/quest/m0/ci/release-gates.md index a90ef11762c..e3cf2cac78b 100644 --- a/quest/m0/ci/release-gates.md +++ b/quest/m0/ci/release-gates.md @@ -2,29 +2,28 @@ ## Goal -`release` carries `.github/workflows/release-gate.yml`, backported now as -release-line maintenance rather than waiting for the next cut (decided -2026-10-22, maintainer). Check with `git show origin/release:.github/workflows/release-gate.yml`. - -Then the maintainer adds `Release gate` from the GitHub Actions integration -(15368) to release ruleset 24392632, beside `Check`, so PRs into `release` -cannot merge until the platform and optional workflows pass. Main ruleset -2420853 already requires only `Check`. +Waiting on the maintainer. [moq-dev/moq#6733](https://github.com/moq-dev/moq/pull/6733) +backports the gate onto `release`'s own workflow set. Once it merges +(check with `git show origin/release:.github/workflows/release-gate.yml`), the +maintainer adds `Release gate` from the GitHub Actions integration (15368) to +release ruleset 24392632, beside `Check`, so PRs into `release` cannot merge +until the platform and optional workflows pass. Main ruleset 2420853 already +requires only `Check`. Delete this quest once the ruleset requires it. ## Plan Decided 2026-10-19: expensive and optional checks are required on `release` and run only nightly on `main`. -- `release-gate.yml` calls Platform, Features, and every path-selected optional - workflow, and its `Release gate` job fails when any of them fails or is - cancelled. Skipped workflows pass it, so one context replaces a list of job - names that each rename would break. `sh/gh/queue.test.ts` holds the policy. +- `release-gate.yml` calls every path-selected optional workflow, and its + `Release gate` job fails when any of them fails or is cancelled. Skipped + workflows pass it, so one context replaces a list of job names that each + rename would break. On `main`, `sh/gh/queue.test.ts` holds the policy. - A release PR runs the workflows merged with `release`, so a PR opened before - the cut never reports `Release gate` and would block once it is required. - Add the context right after the cut merges, then edit the title of each open - release PR; `edited` reruns the gate. -- Before then, release PRs still run the gate; it just does not block. + the backport merges never reports `Release gate` and would block once it is + required. Add the context right after it merges, then edit the title of each + open release PR; `edited` reruns the gate. +- The next cut conflicts on the backported workflow files; take `main`'s side. - Measured 2026-10-14 to 10-16, for sizing the release PR wait: of 100 queue macOS jobs, runner wait was p50 0.2, p90 33 and max 83 minutes. Nightly and releases share the five-job macOS cap.