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 react-native-safe-area-context from 4.10.1 to 4.10.8 #9

Merged

Conversation

SanteriMertakorpi
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade react-native-safe-area-context from 4.10.1 to 4.10.8.

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

  • The recommended version was released on 2 months ago.

Release notes
Package name: react-native-safe-area-context from react-native-safe-area-context 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 react-native-safe-area-context from 4.10.1 to 4.10.8.

See this package in npm:
react-native-safe-area-context

See this project in Snyk:
https://app.snyk.io/org/santerimertakorpi/project/bade501f-8023-47ca-bcf3-5453c4393b2d?utm_source=github&utm_medium=referral&page=upgrade-pr
@SanteriMertakorpi SanteriMertakorpi merged commit fd288a7 into main Sep 19, 2024
2 checks passed
@SanteriMertakorpi SanteriMertakorpi deleted the snyk-upgrade-361d68e313460d23976dffa08320a1f9 branch September 19, 2024 08:28
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