Skip to content

[Snyk] Fix for 2 vulnerabilities - #741

Open
MaxMood96 wants to merge 1 commit into
trunkfrom
snyk-fix-c6276dea1c3c14cc6e8c0b2be0e039c2
Open

[Snyk] Fix for 2 vulnerabilities#741
MaxMood96 wants to merge 1 commit into
trunkfrom
snyk-fix-c6276dea1c3c14cc6e8c0b2be0e039c2

Conversation

@MaxMood96

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
high severity Inefficient Algorithmic Complexity
SNYK-JS-BRACEEXPANSION-17706650
high severity Interpretation Conflict
SNYK-JS-FASTURI-17675102

Breaking Change Risk

Merge Risk: High

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

Copy link
Copy Markdown
Owner Author

Merge Risk: High

This release includes several major version upgrades with significant breaking changes. The upgrades for jest and webpack-dev-server are high-risk and require immediate developer attention, involving code, configuration, and environment updates. Other major upgrades for babel-loader and rimraf introduce strict Node.js version requirements.

Top 3 Most Impactful Upgrades

1. jest 29.7.0 → 30.0.0 (HIGH RISK)

This major upgrade introduces several breaking changes requiring code and environment updates.

  • Node.js Support: Support for Node.js versions 14, 16, 19, and 21 has been dropped. The minimum required version is now 18.
  • Matcher API Changes: Deprecated matcher aliases have been removed (e.g., toBeCalled() is now toHaveBeenCalled()). You can use eslint-plugin-jest with its autofixer to update your codebase automatically.
  • jsdom Upgrade: The jest-environment-jsdom package was upgraded significantly (v21 to v26), which may introduce subtle behavioral changes in the DOM environment and affect tests that mock window.location.
  • Configuration and Snapshots: The --testPathPattern CLI option was renamed to --testPathPatterns, and snapshot formats have changed

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

@mergify

mergify Bot commented Jun 30, 2026

Copy link
Copy Markdown

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

  • Queue this pull request

@github-actions

Copy link
Copy Markdown

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants