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 @types/node from 20.12.7 to 20.12.10 #107

Closed

Conversation

Jeb4dev
Copy link
Contributor

@Jeb4dev Jeb4dev commented May 28, 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 @types/node from 20.12.7 to 20.12.10.

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

  • The recommended version was released on 22 days ago.

Release notes
Package name: @types/node
  • 20.12.10 - 2024-05-06
  • 20.12.9 - 2024-05-06
  • 20.12.8 - 2024-05-01
  • 20.12.7 - 2024-04-09
from @types/node 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 @types/node from 20.12.7 to 20.12.10.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/jeb4dev/project/b6647855-c99a-433f-ab98-42b8e084f067?utm_source=github&utm_medium=referral&page=upgrade-pr
@Jeb4dev Jeb4dev closed this May 29, 2024
@Jeb4dev Jeb4dev deleted the snyk-upgrade-d28335d189b99d917acd0540302ad64e branch May 29, 2024 10:44
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.

None yet

2 participants