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 chart.js from 4.4.3 to 4.4.4 #209

Closed

Conversation

vigneshshettyin
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade chart.js from 4.4.3 to 4.4.4.

ℹ️ 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: chart.js from chart.js 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 chart.js from 4.4.3 to 4.4.4.

See this package in npm:
chart.js

See this project in Snyk:
https://app.snyk.io/org/vigneshshettyin/project/f292640c-2272-4ab3-b7a3-dc7f2f3bba3e?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Oct 5, 2024

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

Name Status Preview Comments Updated (UTC)
eat-my-url ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 5, 2024 0:02am

@vigneshshettyin vigneshshettyin deleted the snyk-upgrade-cbd498e58096463f195b0e437ffe7822 branch November 18, 2024 15:32
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