Skip to content

[Snyk] Security upgrade react-native from 0.78.0 to 0.85.0#22

Open
revan-zhang wants to merge 1 commit intomainfrom
snyk-fix-a9bb812cfe63c5465c2e0b7607403b30
Open

[Snyk] Security upgrade react-native from 0.78.0 to 0.85.0#22
revan-zhang wants to merge 1 commit intomainfrom
snyk-fix-a9bb812cfe63c5465c2e0b7607403b30

Conversation

@revan-zhang
Copy link
Copy Markdown
Contributor

@revan-zhang revan-zhang commented Apr 14, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • example/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
  535  

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.


Open with Devin

@revan-zhang
Copy link
Copy Markdown
Contributor Author

revan-zhang commented Apr 14, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

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

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

Open in Devin Review

Comment thread example/package.json
"dependencies": {
"react": "19.0.0",
"react-native": "0.78.0",
"react-native": "0.85.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔴 Incomplete version upgrade: @react-native/ devDependencies still pinned to 0.78.0 after react-native bump to 0.85.0*

The react-native dependency was bumped from 0.78.0 to 0.85.0, but the corresponding @react-native/* devDependencies (@react-native/babel-preset, @react-native/metro-config, @react-native/typescript-config) at example/package.json:24-26 are still pinned to 0.78.0. In the React Native ecosystem, these packages are versioned in lockstep with react-native itself (note they were all at 0.78.0 before this change, matching the previous react-native version). Running the example app with this mismatch will likely cause build or runtime failures due to incompatible tooling versions. The @react-native-community/cli* packages at 15.0.1 (example/package.json:21-23) were also released for react-native 0.78 and may need updating as well.

Prompt for agents
The react-native dependency in example/package.json was bumped from 0.78.0 to 0.85.0, but the @react-native/* devDependencies were not updated to match. Specifically, @react-native/babel-preset (line 24), @react-native/metro-config (line 25), and @react-native/typescript-config (line 26) are still at 0.78.0. These packages are versioned in lockstep with react-native. Additionally, the @react-native-community/cli packages (lines 21-23) at 15.0.1 were built for RN 0.78 and may also need updating. All these devDependencies should be updated to versions compatible with react-native 0.85.0.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

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