[Snyk] Fix for 1 vulnerabilities

[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
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-18313070

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[MaxMood96]

This upgrade includes a major version update for jest from v29 to v30, which introduces significant breaking changes. The update for markdownlint-cli is a minor version bump but spans a large number of versions, introducing many new linting rules.

jest@29.7.0 → jest@30.0.0

Risk: HIGH

This is a major update with several breaking changes that will likely require code and configuration modifications.

Key Breaking Changes:

• Node.js Version Support: Support for Node.js versions 14, 16, 19, and 21 has been dropped. The minimum required version is now 18.
• TypeScript Version: The minimum supported TypeScript version is now 5.4.
• JSDOM Upgrade: The jest-environment-jsdom package has been upgraded to use jsdom v26 (from v21). This may introduce behavioral changes, especially around mocking window.location.
• Matcher Aliases Removed: Deprecated matcher aliases have been removed (e.g., toBeCalled() is replaced by toHaveBeenCalled()). You can use eslint-plugin-jest to help automate this.
• Snapshot Updates: Snapshots will need to be updated due to formatting changes.
• CLI Argument Renamed: The --testPathPattern argument has been renamed to --testPathPatterns.

Recommendation:
Developers must consult the official migration guide before upgrading. Plan for significant testing and potential refactoring of tests, especially those interacting with the DOM or using removed matcher aliases. Snapshots will need to be regenerated.

Source: Jest 30 Migration Guide, Jest 30 Release Blog Post

markdownlint-cli@0.31.1 → markdownlint-cli@0.49.1

Risk: MEDIUM

While this is a minor version upgrade, it covers a wide range of releases. There are no direct breaking API changes to the CLI tool itself, but it incorporates numerous updates from the underlying markdownlint library. These updates include new linting rules, bug fixes, and stricter enforcement which could cause previously passing builds to fail.

Recommendation:
After upgrading, run the linter on your project and expect to fix new violations. Review the changelog for the markdownlint package for details on new and modified rules.

Source: markdownlint-cli Release History

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.