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 expo from 51.0.18 to 51.0.27 #43

Closed

Conversation

tanyipeng834
Copy link
Collaborator

snyk-top-banner

Snyk has created this PR to upgrade expo from 51.0.18 to 51.0.27.

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

  • The recommended version was released on 21 days ago.

Release notes
Package name: expo
  • 51.0.27 - 2024-08-14
  • 51.0.26 - 2024-08-08
  • 51.0.25 - 2024-08-07
  • 51.0.24 - 2024-07-30
  • 51.0.23 - 2024-07-29
  • 51.0.22 - 2024-07-22
  • 51.0.21 - 2024-07-16
  • 51.0.20 - 2024-07-11
  • 51.0.19 - 2024-07-11
  • 51.0.18 - 2024-07-03
from expo 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 expo from 51.0.18 to 51.0.27.

See this package in npm:
expo

See this project in Snyk:
https://app.snyk.io/org/tanyipeng834/project/9bac7905-6baa-4a36-bd16-4a83744311f9?utm_source=github&utm_medium=referral&page=upgrade-pr
@kengboonang kengboonang deleted the snyk-upgrade-a4b0a87dc4bf5ff03a9dff1198074c54 branch October 24, 2024 13:48
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