Bump the wordpress-packages group across 1 directory with 3 updates

[dependabot]

Bumps the wordpress-packages group with 3 updates in the / directory: @wordpress/e2e-test-utils-playwright, @wordpress/env and @wordpress/scripts.

Updates @wordpress/e2e-test-utils-playwright from 1.46.0 to 1.47.0

Changelog

Sourced from @​wordpress/e2e-test-utils-playwright's changelog.

1.47.0 (2026-05-27)

Commits

• d653c5f chore(release): publish
• 065fa3b Update changelog files
• f63ca66 Merge changes published in the Gutenberg plugin "release/23.3" branch
• 7f4e229 Update changelog files
• b5afac3 Merge changes published in the Gutenberg plugin "release/23.3" branch
• fee7eec Update changelog files
• f34b1f7 Merge changes published in the Gutenberg plugin "release/23.3" branch
• See full diff in compare view

Updates @wordpress/env from 11.6.0 to 11.7.0

Changelog

Sourced from @​wordpress/env's changelog.

11.7.0 (2026-05-27)

Commits

• d653c5f chore(release): publish
• 065fa3b Update changelog files
• f63ca66 Merge changes published in the Gutenberg plugin "release/23.3" branch
• 7f4e229 Update changelog files
• b5afac3 Merge changes published in the Gutenberg plugin "release/23.3" branch
• fee7eec Update changelog files
• See full diff in compare view

Updates @wordpress/scripts from 32.2.0 to 32.3.0

Changelog

Sourced from @​wordpress/scripts's changelog.

32.3.0 (2026-05-27)

Commits

• d653c5f chore(release): publish
• 065fa3b Update changelog files
• f63ca66 Merge changes published in the Gutenberg plugin "release/23.3" branch
• 7f4e229 Update changelog files
• b5afac3 Merge changes published in the Gutenberg plugin "release/23.3" branch
• fee7eec Update changelog files
• f34b1f7 Merge changes published in the Gutenberg plugin "release/23.3" branch
• See full diff in compare view

[mukeshpanchal27]

@dependabot rebase

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: mukeshpanchal27 <mukesh27@git.wordpress.org>
Co-authored-by: westonruter <westonruter@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[mukeshpanchal27]

@dependabot rebase

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.29%. Comparing base (4cbab3d) to head (081f2b3).
⚠️ Report is 1 commits behind head on trunk.

Additional details and impacted files

@@           Coverage Diff           @@
##            trunk    #2509   +/-   ##
=======================================
  Coverage   69.29%   69.29%           
=======================================
  Files          90       90           
  Lines        7723     7723           
=======================================
  Hits         5352     5352           
  Misses       2371     2371           

Flag	Coverage Δ
multisite	69.29% <ø> (ø)
single	35.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[westonruter]

Now looking at the diff. The prettier fixes seem to indicate that @wordpress/scripts is no longer using the fork of Prettier to add additional whitespace.

Seeing the update here:

Updates @wordpress/scripts from 32.2.0 to 32.3.0

I'm confused because there is nothing in the changelog here: https://github.com/WordPress/gutenberg/blob/trunk/packages/scripts/CHANGELOG.md#3230-2026-05-27

It seems something deeper is going on.

[westonruter]

I'm getting Claude to take a look.

[westonruter]

👉🏻 When we merge this, let's use squash and merge to prevent the blame from getting touched after all those files were changed.

[westonruter]

Note

This comment was written by Claude (Claude Code), acting on behalf of @westonruter. It supersedes all my earlier comments (now marked outdated) and reflects the final, verified understanding.

Full summary

This PR tangled together two unrelated problems. Both are now understood; here is the complete picture including a wrong turn that CI corrected.

1. The Prettier reformatting was a lockfile hoisting accident — not a Prettier change

The Fix JS lint errors commit (cb43dc4) reformatted ~26 files from WordPress style (require( 'x' )) to vanilla style (require('x')). No changelog explained it, because nothing changed in any package's Prettier declaration:

• @wordpress/scripts 32.2.0 and 32.3.0 both declare prettier: npm:wp-prettier@3.0.3
• @wordpress/prettier-config 4.46.0 and 4.47.0 both declare prettier: >=3

wp-prettier (the fork) is pulled in by @wordpress/scripts via an alias, while @wordpress/prettier-config / @wordpress/eslint-plugin / eslint-plugin-prettier only ask for prettier: >=3. npm hoists a single prettier to node_modules/prettier (what eslint-plugin-prettier resolves at lint time), and which one wins is effectively a coin flip:

commit	hoisted node_modules/prettier
32ffc9f (dependabot bump)	wp-prettier@3.0.3 ✅
branch HEAD after the e2e revert regenerated the lock	vanilla prettier@3.8.3 ❌

So regenerating the lock to pin e2e flipped the hoist → vanilla Prettier → mass reformatting.

Fix (d2ef6ca): pin the fork so the coin flip can't recur, and revert the reformatting (files now match trunk):

"overrides": { "prettier": "npm:wp-prettier@3.0.3" }

(7adffee cleaned up a few workflow YAML files the reformatter had incidentally touched.) This override is the durable fix and stays regardless of the e2e outcome — without it, the next lockfile regeneration can flip Prettier again. Validation: integrity hashes match the registry, npm ci is clean, idempotent re-resolve yields no diff, and npm audit signatures verifies all packages.

2. The e2e pin to 1.46.0 is genuinely required — 1.47.0 and 1.48.0 are both unusable from npm

The pin was originally attributed to a vague "version mismatch." Investigation (and a deliberately tested wrong turn, confirmed by the now-ungated E2E job) produced the real picture:

e2e version	what it publishes	result with @wordpress/scripts 32.3.0
1.46.0	compiled build/index.cjs	✅ works
1.47.0 (759284c)	neither build nor src	❌ Cannot find module '.../src/index.ts'
1.48.0 (963a515)	raw TS source src/index.ts	❌ SyntaxError: Unexpected token 'export'

Both failures occur in @wordpress/scripts/config/playwright/global-setup.js:9, which does a plain CommonJS require('@wordpress/e2e-test-utils-playwright'):

• 1.47.0 set exports.default to ./src/index.ts but did not include src/ in the published tarball (and dropped the build/index.cjs that 1.46.0 had), so the require resolves to a missing file.
• e2e-test-utils-playwright: add src to published NPM files gutenberg#78847 ("add src to published NPM files", in 1.48.0) added src/ — but the package is now source-only TypeScript, and Playwright's transpiler skips node_modules, so the raw export is never compiled. #78847 therefore traded one breakage for another rather than restoring a consumable package.

Bumping @wordpress/scripts does not help: 32.3.0 and 32.4.0 ship an identical global-setup.js (plain require). So 1.46.0 (compiled CJS) is the only version consumable from npm in this setup, and the pin should remain until upstream ships a compiled build again (not just source).

Resolution (081f2b3): pinned back to 1.46.0 via overrides. The branch is byte-identical to f9c55ed, which previously passed all checks including E2E.

Where this leaves the PR

• ✅ @wordpress/scripts 32.3.0 and @wordpress/env 11.7.0 bumps land as intended.
• ✅ @wordpress/e2e-test-utils-playwright stays pinned at 1.46.0 — for a now-documented reason (1.47.0/1.48.0 are not consumable from npm), not a vague "mismatch."
• ✅ prettier override keeps wp-prettier hoisted deterministically.

Recommended follow-ups

1. Report upstream in WordPress/gutenberg: @wordpress/e2e-test-utils-playwright ≥1.47.0 is not consumable as an npm dependency — 1.47.0 omits an entry point entirely, and 1.48.0 publishes source-only TS that consuming Playwright setups can't transpile from node_modules. #78847 did not fully resolve this. Keep the e2e bump pinned at 1.46.0 until a release ships a compiled entry point again.
2. Consider raising the underlying Prettier fragility (fork-via-alias vs. >=3 peers, which lets npm hoist either one) upstream so the override isn't needed indefinitely.