Update dependencies - #464
Open
KevinBatdorf wants to merge 4 commits into
Open
Conversation
Nightly runs fail a couple times a week with one-off WP Playground errors — a 500 on a front-end request, a crashed evaluate — hitting a different spec each time while the rest of the matrix passes. Those aren't plugin regressions, but each one sends a failure email that has to be triaged by hand. Gate the retry on CI so local runs keep retries: 0 and still fail fast on first error; a genuinely broken test still fails CI after its retry. Update the testing rules to match — they previously banned retries outright. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ncu with two documented holds. shiki stays on 0.14.7: the vendored build/shiki assets and the 0.14 API the block is built around don't survive shiki 1+ — that migration is its own project. tailwindcss stays on 3.4: v4 removed tailwindcss/nesting from exports, which postcss.config.js loads. copy-to-clipboard stays on 3.3.3: v4 made the clipboard e2e tests receive stale copy contents (previous block's code), reproducibly across runs. Everything else moves: wp-scripts 34, typescript 7, block-editor 16, components 38, element 8, biome 2.5, playwright 1.62, playground CLI 3.1.48. Removed the deprecated @types/wordpress__blocks stub. Fallout fixed: block-editor 16 types its store (stale ts-expect-error directives removed, getBlock null handled), components 38 accepts string font sizes (FontSelect's blanket directives removed), typescript 7's stricter indexing needed languages typed as Partial<Record<Lang, string>>, and the new transform callback types take unknown args. Biome 2.5 flagged one dead suppression in a spec. Full suite: 49/49 on latest and nightly (nightly clean on first attempt, no retries). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Locks written by npm 11.6 fail npm ci validation on CI's newer npm (wasm-variant optional deps resolve differently) — regenerated from scratch and verified npm ci passes. actions/cache v5 clears the runner's node20 deprecation warning. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
ncuwith three documented holds, each verified by the suite:build/shikiassets and 0.14 API don't survive shiki 1+; that migration is its own projecttailwindcss/nestingfrom exportsEverything else moves: wp-scripts 34, typescript 7, block-editor 16 (store finally typed — stale directives removed), components 38 (FontSelect's blanket
ts-expect-errors removed), element 8, biome 2.5, playwright 1.62.Full suite 49/49 on latest and nightly, first-attempt clean. Stacks on #463 — merge that first.
🤖 Generated with Claude Code