[Snyk] Fix for 1 vulnerabilities

[ggazzo]

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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-XMLDOMXMLDOM-19498551

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:

🦉 Regular Expression Denial of Service (ReDoS)

[ggazzo]

The upgrade to Expo SDK 55 is a major update with significant breaking changes that require developer action. The version for expo-notifications has been aligned with the main SDK version.

Key Breaking Changes:

• Legacy Architecture Removed: Support for the Legacy React Native Architecture has been completely dropped. The New Architecture (Fabric) is now mandatory. Projects that have not yet migrated will fail to build and require a migration. The newArchEnabled flag in app.json is no longer used.

• notification Field Removed from app.json: The notification configuration key in app.json has been removed. Attempting to build with this key will result in an error. You must migrate this configuration to the expo-notifications config plugin.

• Push Notifications in Expo Go (Android): Testing push notifications in the Expo Go app on Android will now throw an error instead of a warning. Developers must use a custom development build to test push notification functionality.

• New Versioning Scheme: All Expo packages, including expo-notifications, now share the same major version as the SDK. This clarifies compatibility but signifies that packages are generally not cross-compatible between major SDK releases.

Recommendation:

This upgrade requires careful planning. Before upgrading, ensure your application is already migrated to and compatible with the New Architecture. You must also update your notification configuration to use the config plugin instead of app.json.

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

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: cd39bc96-d50d-47c6-8eaa-dc7dbd807f2f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}