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 lucide-react from 0.439.0 to 0.440.0 #134

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Osadhi
Copy link
Owner

@Osadhi Osadhi commented Oct 3, 2024

snyk-top-banner

Snyk has created this PR to upgrade lucide-react from 0.439.0 to 0.440.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 1 version ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: lucide-react from lucide-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 lucide-react from 0.439.0 to 0.440.0.

See this package in npm:
lucide-react

See this project in Snyk:
https://app.snyk.io/org/osadhiv/project/9f50d16c-1031-4776-ae5e-c084e26c6e3c?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Oct 3, 2024

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

Name Status Preview Comments Updated (UTC)
insta-track ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 3, 2024 11:13am

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