Skip to content

Conversation

@sojan-official
Copy link
Member

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 Score
medium severity Prototype Pollution
SNYK-JS-JSYAML-13961110
  631  

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:

🦉 Prototype Pollution

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-JSYAML-13961110
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

"react": "18.3.1",
"react-hook-form": "^7.52.1",
"react-native": "0.76.9",
"react-native": "0.81.0",

Choose a reason for hiding this comment

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

P1 Badge Keep React Native aligned with Expo SDK 52

Expo SDK 52 is built and published against React Native 0.76.x; bumping react-native to 0.81.0 while keeping expo at ~52.0.46 will cause peer-dependency resolution failures (and native build incompatibilities) during pnpm install/expo prebuild, because the Expo packages still require 0.76.x. Please keep React Native at the SDK-supported version or upgrade the entire Expo SDK to a release that supports 0.81.x.

Useful? React with 👍 / 👎.

"react": "18.3.1",
"react-hook-form": "^7.52.1",
"react-native": "0.76.9",
"react-native": "0.81.0",

Choose a reason for hiding this comment

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

P1 Badge Update pnpm-lock after React Native version bump

Changing react-native to 0.81.0 without regenerating pnpm-lock.yaml leaves the lockfile pinned to 0.76.9; any CI run using pnpm install --frozen-lockfile will now fail because the lockfile no longer matches package.json, and even unfrozen installs will continue to resolve the older version. Regenerate the pnpm lockfile so installs pick up the new React Native release.

Useful? React with 👍 / 👎.

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