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 22.10.2 to 22.10.5 #1917

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

qdraw
Copy link
Owner

@qdraw qdraw commented Jan 28, 2025

snyk-top-banner

Snyk has created this PR to upgrade @types/node from 22.10.2 to 22.10.5.

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

Release notes
Package name: @types/node
  • 22.10.5 - 2025-01-03
  • 22.10.4 - 2025-01-02
  • 22.10.3 - 2025-01-01
  • 22.10.2 - 2024-12-11
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 22.10.2 to 22.10.5.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/qdraw/project/3eed192c-1a65-4594-8052-8d49e13d7314?utm_source=github&utm_medium=referral&page=upgrade-pr
@qdraw qdraw merged commit e63a6c0 into master Jan 30, 2025
6 checks passed
@qdraw qdraw deleted the snyk-upgrade-825b4da184df8b7b2aaaf22240089294 branch January 30, 2025 13:39
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