test(e2e): pin @wp-playground/cli to 3.1.40 to escape upstream regression#64
Merged
Conversation
…sion The Playwright Playground smoke job has failed for hours across main and every branch: the Playground server boots but wp-admin times out, failing different tests each run. @wp-playground/cli@3.1.41 published 2026-06-22 11:32 UTC and has been flaky/failing since; 3.1.40 ran green on main earlier the same day. The floating @latest in the E2E harness pulled the regressed release into every run. Pin the CLI to 3.1.40 across all four E2E scripts so CI is deterministic and escapes the bad release. Temporary: revert to @latest (or bump) once a fixed Playground CLI ships past 3.1.41. Skill-doc @latest examples are left as-is. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #64 +/- ##
=======================================
Coverage 80.80% 80.80%
=======================================
Files 44 44
Lines 3084 3084
Branches 523 523
=======================================
Hits 2492 2492
Misses 185 185
Partials 407 407 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Playwright Playground smoke job has failed for ~7+ hours across
mainand every branch. The Playground server boots, but wp-admin pages time out (ensurePluginActivated→ "Plugins" h1, and editor/inserter), failing different tests each run — a hallmark of an unstable environment, not repo code. Runtime-matrix Docker jobs + PHPUnit stayed green throughout.Root cause
The E2E harness boots the Playground via floating
@wp-playground/cli@latest.3.1.41published 2026-06-22 11:32 UTC and has been flaky/failing ever since; the prior3.1.40ran green onmainearlier the same day (runs at 02:19 and 03:34 UTC). Floating@latestsilently pulled the regressed release into every CI run, with no signal that anything in the repo changed.Fix
Pin the CLI to
3.1.40across all four E2E scripts:scripts/test-playground-e2e.shscripts/test-a11y.shscripts/test-lifecycle-e2e.sh(×2)scripts/test-smoke-e2e.shThis makes CI deterministic and escapes the bad release. This PR's own CI run is the experiment: if the Playground smoke job goes green here, it both unblocks CI and confirms 3.1.41 as the regression.
The
@latestreferences in.github/skills/wp-playground/docs are intentionally left as general usage examples.Temporary
This is a deliberate pin to dodge a bad upstream release. Once a fixed
@wp-playground/cliships past 3.1.41, follow up to bump or return to floating so the scripts don't rot on an old version.🤖 Generated with Claude Code