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 18.19.38 to 18.19.39 #136

Merged
merged 1 commit into from
Jul 20, 2024

Conversation

AntonUden
Copy link
Contributor

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 18.19.38 to 18.19.39.

ℹ️ 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 22 days ago.

Release notes
Package name: @types/node
  • 18.19.39 - 2024-06-22
  • 18.19.38 - 2024-06-20
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 18.19.38 to 18.19.39.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/antonuden/project/49e78096-1d76-46d5-b4f7-6a9ce5b182fd?utm_source=github&utm_medium=referral&page=upgrade-pr
@AntonUden AntonUden merged commit 61db6f4 into main Jul 20, 2024
8 of 10 checks passed
@AntonUden AntonUden deleted the snyk-upgrade-6205a9a0a69cdaff65d274a589a714d8 branch July 20, 2024 00:28
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