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 @vercel/speed-insights from 1.0.11 to 1.0.12 #231

Closed

Conversation

thearyadev
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @vercel/speed-insights from 1.0.11 to 1.0.12.

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

  • The recommended version was released on a month ago.

Release notes
Package name: @vercel/speed-insights from @vercel/speed-insights 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 @vercel/speed-insights from 1.0.11 to 1.0.12.

See this package in npm:
@vercel/speed-insights

See this project in Snyk:
https://app.snyk.io/org/thearyadev/project/556003a2-23d0-448e-beb7-86dc60c30428?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Jul 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
top500-aggregator ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 26, 2024 9:24am

@thearyadev thearyadev closed this Sep 11, 2024
@thearyadev thearyadev deleted the snyk-upgrade-076aa0c04c8a9b4efa6b2ea469e99d07 branch September 12, 2024 17:54
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