[desrosj]

Updates ten development dependencies for WordPress 7.2 and refreshes the lockfile against current trunk.

This refresh preserves Playwright 1.64.1, landed in 64740, along with trunk’s current Node requirements and dependency changes. The earlier Playwright bump is no longer part of this PR.

• @types/codemirror: 5.60.17 → 5.60.18
• @wordpress/e2e-test-utils-playwright: 1.51.0 → 1.52.0
• @wordpress/prettier-config: 4.51.0 → 4.52.0
• @wordpress/scripts: 33.0.0 → 34.0.0
• autoprefixer: 10.5.3 → 10.5.4
• grunt: 1.6.2 → 1.6.3
• postcss: 8.5.19 → 8.5.25
• sass: 1.101.0 → 1.102.0
• wait-on: 9.0.10 → 9.1.0
• webpack: 5.108.4 → 5.109.2

Trac ticket: https://core.trac.wordpress.org/ticket/65857

Validation of the refresh

• npm ci passed; the updated packages share Playwright 1.64.1.
• npm run grunt qunit:compiled passed: 704 QUnit tests against compiled scripts and 704 against uncompiled scripts.
• npm run build:dev, npm run typecheck:js, and npm run lint:jsdoc passed.
• E2E, performance, and visual test discovery passed.
• Dashboard and comment moderation browser checks passed: 14 tests, single-site Chromium, no retries.
• GitHub Actions checks are pending for the refresh commit.

Use of AI Tools

The original patch disclosed no AI use. The follow-up refresh used Codex (gpt-6) to resolve conflicts with trunk, regenerate the lockfile, run validation, and update this description under Lance Willett’s direction.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[desrosj]

There's a few issues to look into before this can be committed.

• I've been seeing some webpack-related failures locally. This needs to be properly investigated.
• There are CSS changes that result in the built CSS files. They seem related to the changes in 1.101.4 for the sass dependency.

[mukeshpanchal27]

@desrosj Can you make this ready for 7.2? As it's not committed in 7.1.