[Snyk] Security upgrade @wordpress/scripts from 33.0.0 to 34.0.0

[MaxMood96]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18512280
	Interpretation Conflict SNYK-JS-FASTURI-18506908

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:

🦉 Allocation of Resources Without Limits or Throttling

[MaxMood96]

This is a major version upgrade for the primary development toolkit for WordPress projects.

While specific release notes for version 34.0.0 were not found, a common breaking change for this package is dropping support for older, end-of-life Node.js versions. The package's official documentation states it requires a Node.js version with Long-Term Support (LTS) status. The current development branch requires Node.js v18.12.0 or newer.

Potential Breaking Change:

• Node.js Version: It is highly likely that this version drops support for Node.js 16 (EoL September 2023) or older versions. Projects using older Node.js environments will likely fail to install or run this updated package.

Recommendation:
Ensure your development and build environments are running a current Node.js LTS version (e.g., v18.x or v20.x) before upgrading. The risk is medium as this is an environment change that requires verification but should not require code modifications if your Node.js version is already up-to-date.

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.

[github-actions]

Size Change: 0 B

Total Size: 7.78 MB

_{compressed-size-action}