Skip to content

[Snyk] Upgrade react from 19.0.0 to 19.2.0#69

Open
g4rcez wants to merge 1 commit intomainfrom
snyk-upgrade-2d26a693781fda1f14ab4890d6104f82
Open

[Snyk] Upgrade react from 19.0.0 to 19.2.0#69
g4rcez wants to merge 1 commit intomainfrom
snyk-upgrade-2d26a693781fda1f14ab4890d6104f82

Conversation

@g4rcez
Copy link
Copy Markdown
Owner

@g4rcez g4rcez commented Nov 4, 2025

snyk-top-banner

Snyk has created this PR to upgrade react from 19.0.0 to 19.2.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 219 versions ahead of your current version.

  • The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BABELRUNTIME-10044504
452 Proof of Concept

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade react from 19.0.0 to 19.2.0.

See this package in pnpm:
react

See this project in Snyk:
https://app.snyk.io/org/g4rcez/project/7cee4652-e1fb-48c9-8ecf-91caaf5bbf68?utm_source=github&utm_medium=referral&page=upgrade-pr
@vercel
Copy link
Copy Markdown

vercel Bot commented Nov 4, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
brouther Error Error Nov 4, 2025 6:23am

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