From 1afc8f81ce908f8a3c0838ebf6ea54be76de02c9 Mon Sep 17 00:00:00 2001 From: Robert O'Rourke Date: Wed, 28 Oct 2026 10:19:32 +0000 Subject: [PATCH] Docs: list WP 7.0 and 7.1 as blocking lanes The workflow's DEFAULT_BLOCKING already holds 6.9, 7.0 and 7.1, moved there when the 7.x test fixes landed in #31, and main's last Playwright run passed on all three as blocking lanes. CLAUDE.md still described 7.0 and 7.1 as experimental lanes with known failures, which would mislead anyone reading it before touching CI. Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 34c8dbc..8b6ee55 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -154,13 +154,13 @@ Tests use `@wordpress/env`, configured in `.wp-env.json`. The environment includ | Lane | Core | Job | Blocking | | --- | --- | --- | --- | | `6.9` | `WordPress/WordPress#6.9.7` | `e2e` | yes | -| `7.0` | `WordPress/WordPress#7.0.4` | `e2e-experimental` | no | -| `7.1` | `WordPress/WordPress#7.1` | `e2e-experimental` | no | +| `7.0` | `WordPress/WordPress#7.0.4` | `e2e` | yes | +| `7.1` | `WordPress/WordPress#7.1` | `e2e` | yes | | `nightly` | `WordPress/WordPress#master` | `e2e-experimental` | no | -A failure in a non-blocking lane surfaces as a `::warning::` annotation and a job summary. For `nightly` that is early warning of an upstream change; for `7.0`/`7.1` it is a known compatibility gap. +A failure in the non-blocking `nightly` lane surfaces as a `::warning::` annotation and a job summary. It is early warning of an upstream change, not a defect in the commit under test. -**7.0 and 7.1 are non-blocking only until the WordPress 7.x gaps are closed.** They run on every PR and report, but the suite genuinely fails on 7.x — the plugin's `core/query` inspector panels are not found in the 7.x site editor, and 7.1 additionally fails `multiple-post-templates` and a *frontend* preset assertion that cannot be a selector problem. Move them back into `DEFAULT_BLOCKING` in the `lanes` job once that is fixed. Lanes carry a `comment` flag so `nightly` stays out of the PR thread while the released versions report into it. +Lanes carry a `comment` flag so `nightly` stays out of the PR thread while the released versions report into it. Three structural points, each of which fixes a bug that actually happened: