[Snyk] Security upgrade puppeteer-core from 23.11.1 to 25.0.2

[MaxMood96]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• packages/scripts/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Directory Traversal SNYK-JS-EXTRACTZIP-17660777

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Directory Traversal

[MaxMood96]

This is a major version upgrade from v23 to v25 which introduces significant breaking changes, most notably the library is now ESM-only.

Key Breaking Changes in v25.0.0:

• ESM Only: The package has been converted to an ES Module (ESM) only package. You must now use import puppeteer from 'puppeteer-core' instead of require(). This may require updating your project's configuration (e.g., adding "type": "module" to package.json). [1, 2]
• Node.js Version: The minimum required Node.js version has been increased to v20.19.1, with a further bump to Node.js v22 noted in the changelog. [1, 2, 9]
• Asynchronous Methods: Functions like executablePath() and defaultArgs() now return a Promise instead of a synchronous value. Calls to these methods must be updated with await. [1, 2]
• Removed APIs: Deprecated methods and properties have been removed, including Browser.isConnected(), MouseOptions.clickCount, and the sameParty cookie attribute. [2]

Recommendation:
Due to the move to ESM-only and the Node.js version requirement, this upgrade will likely require significant refactoring. It is recommended to review your project's build system and module resolution. Ensure your environment meets the new Node.js version requirement and update all calls to newly asynchronous methods.

Source: Puppeteer Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @snyk-bot, @MaxMood96, @mergify.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

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

Unlinked contributors: snyk-bot, MaxMood96, mergify.

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