Skip to content

[Snyk] Fix for 1 vulnerabilities#68

Open
lposen wants to merge 1 commit into
mainfrom
snyk-fix-4e8e1801218ed4bfd5a4ad4f185eb360
Open

[Snyk] Fix for 1 vulnerabilities#68
lposen wants to merge 1 commit into
mainfrom
snyk-fix-4e8e1801218ed4bfd5a4ad4f185eb360

Conversation

@lposen

@lposen lposen commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

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

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.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Inefficient Algorithmic Complexity
SNYK-JS-BRACEEXPANSION-17706650

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 June 30, 2026 18:23
@lposen

lposen commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator Author

Merge Risk: High

This upgrade includes several major version jumps for critical packages like ESLint, React Native, and Expo, each introducing significant breaking changes. These updates require mandatory configuration changes, code refactoring, and a strategic migration to the New React Native Architecture.

Top 3 Most Impactful Upgrades

1. eslint 8.57.110.0.0 (High Risk)

This update spans two major versions and completely overhauls ESLint's configuration system.

  • Mandatory Configuration Migration: The traditional .eslintrc.js format is no longer supported in v10. You must migrate your configuration to the new "flat config" format (eslint.config.js). This is a significant change that requires rewriting your entire ESLint setup.
  • Node.js Requirement: Support for Node.js versions older than 20.19.0 has been dropped.
  • Complete Removal of eslintrc: ESLint v10 completely removes the old configuration system and the ESLINT_USE_FLAT_CONFIG environment variable used for backward compatibility in v9.

Recommendation: Use the npx eslint --init command to generate a new eslint.config.js file and manually migrate your existing rules, plugins, and parser configurations. This is a prerequisite for the upgrade.

2. react-native 0.79.50.85.0 (High Risk)

This is a very large version jump that forces a migration to React Native's New Architecture and includes numerous breaking changes across several releases.

  • New Architecture is Mandatory: Starting with v0.82, the New Architecture (Fabric and TurboModules) is the only supported runtime. The ability to opt out has been removed.
  • Interop Layer Removed: Version 0.85 removes the compatibility layer that allowed older, non-migrated libraries to function under the New Architecture. This will cause libraries that have not been fully updated to break.
  • Key Breaking Changes:
    • The built-in Jest preset has been moved to a separate package (`@react-native/

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

@qltysh

qltysh Bot commented Jun 30, 2026

Copy link
Copy Markdown

Qlty


⚠️ Comments skipped @lposen doesn't have a Qlty seat in Iterable.

Qlty doesn't post analysis or coverage comments for contributors without a seat. An authorized user can grant @lposen a seat from this pull request's page in Qlty.

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