Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @babel/preset-react from 7.25.7 to 7.26.3 #224

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

MelvinBot
Copy link

snyk-top-banner

Snyk has created this PR to upgrade @babel/preset-react from 7.25.7 to 7.26.3.

ℹ️ 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 2 versions ahead of your current version.

  • The recommended version was released a month ago.

Release notes
Package name: @babel/preset-react from @babel/preset-react GitHub release notes

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.

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 @babel/preset-react from 7.25.7 to 7.26.3.

See this package in npm:
@babel/preset-react

See this project in Snyk:
https://app.snyk.io/org/expensify/project/35c87b83-0578-438a-9ce5-96d21d712614?utm_source=github&utm_medium=referral&page=upgrade-pr
@mjasikowski
Copy link
Contributor

Not an emergency, just the Snyk assign-to-puller-bear action was failing here.

@mjasikowski mjasikowski merged commit e410206 into main Jan 13, 2025
3 of 4 checks passed
@mjasikowski mjasikowski deleted the snyk-upgrade-2cb4c34a9467e0904133c0b806111fc3 branch January 13, 2025 11:46
@melvin-bot melvin-bot bot added the Emergency label Jan 13, 2025
Copy link

melvin-bot bot commented Jan 13, 2025

@mjasikowski looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

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