Skip to content

[Snyk] Fix for 2 vulnerabilities#67

Open
lposen wants to merge 1 commit into
mainfrom
snyk-fix-9c0074c96b5114dca5324c68ed8347fc
Open

[Snyk] Fix for 2 vulnerabilities#67
lposen wants to merge 1 commit into
mainfrom
snyk-fix-9c0074c96b5114dca5324c68ed8347fc

Conversation

@lposen

@lposen lposen commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

snyk-top-banner

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

Snyk changed the following file(s):

  • example/package.json
  • example/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
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.

@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 is a major upgrade across the entire Expo and React Native stack, moving from Expo SDK 53 to 56 and React Native 0.79 to 0.84. It introduces significant breaking changes that require mandatory code and environment updates. The risk is high due to the architectural shift and widespread API changes.

Key Breaking Changes:

  • New Architecture is Mandatory: Starting with Expo SDK 55 (which uses React Native 0.83), support for the Legacy Architecture has been completely removed. Your application must be migrated to the New Architecture (Fabric/TurboModules) to function.

  • Expo Router Fork from React Navigation: In Expo SDK 56, Expo Router no longer uses React Navigation as a direct dependency. All navigation-related imports must be updated.

    • Before: import { useNavigation } from '@react-navigation/native';
    • After: import { useNavigation } from 'expo-router';
  • Environment and Build Tool Requirements:

    • Node.js: React Native 0.84 requires Node.js v2

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