Skip to content

[Snyk] Fix for 1 vulnerabilities - #944

Open
lposen wants to merge 1 commit into
masterfrom
snyk-fix-6a7c4d56e2f6a70ba247fe501656d2b5
Open

lposen wants to merge 1 commit into
masterfrom
snyk-fix-6a7c4d56e2f6a70ba247fe501656d2b5

Conversation

@lposen

@lposen lposen commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
  • yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Asymmetric Resource Consumption (Amplification)
SNYK-JS-MINIMATCH-22111072
  49  

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.

@lposen
lposen requested a review from a team as a code owner November 16, 2026 11:02
@lposen

lposen commented Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This upgrade to eslint v10 and prettier-eslint v17 introduces significant breaking changes, primarily driven by ESLint. A full migration of your configuration is required.

eslint@9.39.5 → eslint@10.15.0

This is a HIGH RISK upgrade that requires immediate action. ESLint v10 completely removes the legacy .eslintrc configuration system.

Key Breaking Changes:

  • Mandatory Flat Config: Support for .eslintrc.* files has been completely removed. You must migrate your configuration to a single eslint.config.js file.
  • Node.js Version: Support for Node.js versions older than v20.19.0 has been dropped. Your development and CI/CD environments must be updated.
  • Removed CLI Flags & Comments: Legacy CLI flags (e.g., --ignore-path, --env) and /* eslint-env */ comments are no longer supported and will cause errors.
  • New Config Lookup: ESLint now finds the configuration by searching up from the directory of each linted file, which improves behavior in monorepos.

prettier-eslint@16.4.2 → prettier-eslint@17.0.0

This is a MEDIUM RISK upgrade, with the primary change being alignment with ESLint 10. While it has few breaking changes of its own, it is a necessary update for ESLint 10 compatibility and will only work with the new flat config system.

Recommendation:

  1. Run the Migration Script: Use the official ESLint migration tool to convert your existing configuration:
    npx @eslint/migrate-config  
  2. Update Node.js: Ensure your environments are running Node.js v20.19.0 or later.
  3. Review and Test: The migration script is a starting point. You will need to review the generated eslint.config.js and test your linting process thoroughly to ensure all rules and plugins are working as expected.

Source: ESLint v10 Migration Guide, ESLint v10 Release Notes

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

Copilot AI balanced review requested due to automatic review settings November 16, 2026 11:02

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The lockfile omits the still-declared example workspace and its dependencies, causing CI’s immutable Yarn install to fail on a cache miss.

No open issues 🎉

What changed in this PR

This Snyk-generated PR upgrades the React Native SDK’s linting and formatting dependencies to address a reported minimatch resource-consumption vulnerability.

Changes:

  • Raises ESLint to ^10.15.0 and prettier-eslint to ^17.0.0.
  • Refreshes transitive dependencies, including minimatch 11.0.8 for ESLint, and updates lockfile patch resolutions.
File Description
yarn.lock Updates tooling dependencies and patch resolutions; removes example-workspace entries.
package.json Raises the ESLint and prettier-eslint dependency ranges.

Review effort: Balanced

This branch has not been deployed

No deployments
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.

3 participants