From bfad74870e3478d34cdd85815a0b80d19c2245ff Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 12:52:49 -0800 Subject: [PATCH] quest: clear the routes-epic move's wait and note the playwright bump's approval Co-Authored-By: Claude Opus 5.5 --- .../cluster-routing/routes/playwright-pin.md | 5 +++-- quest/m2/promote-cluster-routes.md | 18 ++++++------------ 2 files changed, 9 insertions(+), 14 deletions(-) diff --git a/quest/m2/cluster-routing/routes/playwright-pin.md b/quest/m2/cluster-routing/routes/playwright-pin.md index 64d12908f2e..a107ae81059 100644 --- a/quest/m2/cluster-routing/routes/playwright-pin.md +++ b/quest/m2/cluster-routing/routes/playwright-pin.md @@ -41,8 +41,9 @@ rebuild and pin browser binaries outside nixpkgs. kixelated/nixpkgs fork the same day, [NixOS/nixpkgs#585789](https://github.com/NixOS/nixpkgs/pull/585789) (it also fixes `update.sh` for 1.65's SHA-pinned driver version and rebases the - python driver patch). Advance it by answering that PR's review; then wait - for it to reach `nixpkgs-unstable`. Decided 2026-11-11 (maintainer, + python driver patch). A reviewer approved it on 2026-11-12, so it waits + for a nixpkgs committer to merge it, then for it to reach + `nixpkgs-unstable`. Decided 2026-11-11 (maintainer, /quest-unblock): an agent drafts each review fix on the fork's branch with an `Assisted-by:` trailer, as nixpkgs' CONTRIBUTING.md requires, plus a separate AI-disclosure line in the reply itself, which that policy requires apart from commits; the diff --git a/quest/m2/promote-cluster-routes.md b/quest/m2/promote-cluster-routes.md index 97dd59ad40c..f1e100a5e2d 100644 --- a/quest/m2/promote-cluster-routes.md +++ b/quest/m2/promote-cluster-routes.md @@ -16,15 +16,9 @@ sibling in its milestone (rejected: merge its quests into the parent). The same PR that planned this promoted `quest/m4/kio-channel-contention/` and `quest/m4/stream-transports/` out of `quest/m4/perf/`. -This one waits because `quest mv` refuses to move a quest with an open PR: -the PR's branch is named after the quest's path. Once they land, run -`quest mv quest/m2/cluster-routing/routes quest/m2/cluster-routes` and start -no new quest under the old path first. - -## Waiting - -- moq-dev/moq: the open PRs under `quest/m2/cluster-routing/routes/` land or - close (only [#8443](https://github.com/moq-dev/moq/pull/8443) on - 2026-11-10). Check - with `gh pr list -R moq-dev/moq --search "head:quest/m2/cluster-routing/routes/"` - printing nothing. +It waited because `quest mv` refuses to move a quest with an open PR: the +PR's branch is named after the quest's path. Checked 2026-11-12 +(/quest-unblock): no open PR's head is under +`quest/m2/cluster-routing/routes/`. Run +`quest mv quest/m2/cluster-routing/routes quest/m2/cluster-routes` before any +quest under the old path is started.