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 pino from 8.16.1 to 8.21.0 #778

Merged
merged 1 commit into from
Jul 5, 2024

Conversation

johanbook
Copy link
Owner

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 pino from 8.16.1 to 8.21.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 8 versions ahead of your current version.

  • The recommended version was released on 2 months ago.

Release notes
Package name: pino from pino 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 pino from 8.16.1 to 8.21.0.

See this package in npm:
pino

See this project in Snyk:
https://app.snyk.io/org/johanbook/project/6816372a-9c12-4c50-8594-97a8b7623908?utm_source=github&utm_medium=referral&page=upgrade-pr
@johanbook johanbook merged commit 39b91bc into main Jul 5, 2024
5 checks passed
@johanbook johanbook deleted the snyk-upgrade-71c56eee148a4dc29cc3e3cd4664fa0d branch July 5, 2024 19:37
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