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 svelte-local-storage-store from 0.5.0 to 0.6.3 #4618

Closed
wants to merge 1 commit into from

Conversation

etnoy
Copy link
Contributor

@etnoy etnoy commented Oct 24, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade svelte-local-storage-store from 0.5.0 to 0.6.3.

ℹ️ 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 4 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2023-10-02.
Release notes
Package name: svelte-local-storage-store from svelte-local-storage-store GitHub release notes
Commit messages
Package name: svelte-local-storage-store

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@vercel
Copy link

vercel bot commented Oct 24, 2023

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

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
immich ⬜️ Ignored (Inspect) Visit Preview Oct 24, 2023 8:44am

@etnoy etnoy closed this Oct 24, 2023
@jrasm91 jrasm91 deleted the snyk-upgrade-ae2c451f122af26a3bd653991272e317 branch January 22, 2024 15:15
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