chore(deps-dev): bump @wordpress/scripts from 32.6.0 to 34.0.0

[dependabot]

Bumps @wordpress/scripts from 32.6.0 to 34.0.0.

Changelog

Sourced from @​wordpress/scripts's changelog.

34.0.0 (2026-07-29)

Breaking Changes

• Upgrade the bundled Jest packages from v29 to v30 (#80767).

Enhancements

• `format`: Detect `prettier.config.mjs` so the bundled default config is not used when one is present ([#80422](https://github.com/WordPress/gutenberg/pull/80422)).
  

33.0.0 (2026-07-14)

Breaking Changes

• The test-e2e command now runs the Playwright-based end-to-end test runner instead of Puppeteer (test-playwright remains available as an alias). Removed the Puppeteer test environment and configuration (jest-environment-puppeteer, jest-e2e.config.js, puppeteer.config.js) along with the puppeteer-core and expect-puppeteer dependencies. Puppeteer-specific options (e.g. --puppeteer-interactive, --puppeteer-devtools) are no longer supported (#60357).

Enhancements

• Widen React peer dependency ranges to ^18 || ^19 to support both React 18 and React 19 environments (#80024).
• Update stylelint to ^16.26.1 (#79648).
• Widen the @playwright/test peer dependency to >=1 and mark it optional, so consumers aren't forced to bump Playwright or satisfy it under strict peer deps (#78632).
• Update webpack-dev-server to ^5.2.1, resolving several Dependabot security alerts and migrating the internal dev-server proxy config to the v5 array format (#80347).

Commits

• 7e8b17a chore(release): publish
• 42ad080 Update changelog files
• edffa74 Merge changes published in the Gutenberg plugin "release/23.7" branch
• e9a74f9 chore(release): publish
• 2a0c375 Update changelog files
• e61c854 Merge changes published in the Gutenberg plugin "release/23.6" branch
• 1055a35 Update changelog files
• 8ca3e8e Merge changes published in the Gutenberg plugin "release/23.6" branch
• See full diff in compare view

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​wordpress/​i18n@​6.23.0 ⏵ 6.26.0	+1
	npm/​@​wordpress/​scripts@​32.6.0 ⏵ 34.0.0	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@wordpress/scripts@34.0.0 → npm/webpack@5.109.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.109.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@wordpress/scripts@34.0.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report