Skip to content

Docs: list WP 7.0 and 7.1 as blocking lanes #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roborourke merged 1 commit into from
Oct 29, 2026
Merged

Docs: list WP 7.0 and 7.1 as blocking lanes #43

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
Loading