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 viem from 2.9.29 to 2.9.31 #109

Merged
merged 1 commit into from
May 29, 2024

Conversation

MTthoas
Copy link
Owner

@MTthoas MTthoas commented May 27, 2024

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


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade viem from 2.9.29 to 2.9.31.

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

  • The recommended version was released on 25 days ago.

Release notes
Package name: viem
  • 2.9.31 - 2024-05-02
  • 2.9.30 - 2024-05-02
  • 2.9.29 - 2024-04-30
from viem 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 viem from 2.9.29 to 2.9.31.

See this package in npm:
viem

See this project in Snyk:
https://app.snyk.io/org/mtthoas/project/b51bbbf1-962e-4f24-8a14-61d1af84ef3e?utm_source=github&utm_medium=referral&page=upgrade-pr
@MTthoas MTthoas merged commit 18ffef3 into main May 29, 2024
5 checks passed
@MTthoas MTthoas deleted the snyk-upgrade-df708a63f4153b0c407a373342837323 branch May 29, 2024 10:09
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