Skip to content
This repository was archived by the owner on Dec 22, 2025. It is now read-only.

[Snyk] Upgrade @types/node from 16.11.56 to 16.18.3#75

Open
john-dot-oa wants to merge 1 commit into
masterfrom
snyk-upgrade-dc8f914e7f894b6f73b1becf991df9ff
Open

[Snyk] Upgrade @types/node from 16.11.56 to 16.18.3#75
john-dot-oa wants to merge 1 commit into
masterfrom
snyk-upgrade-dc8f914e7f894b6f73b1becf991df9ff

Conversation

@john-dot-oa

Copy link
Copy Markdown
Contributor

Snyk has created this PR to upgrade @types/node from 16.11.56 to 16.18.3.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

✨ Snyk has automatically assigned this pull request, set who gets assigned.

ℹ️ 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 16 versions ahead of your current version.
  • The recommended version was released 25 days ago, on 2022-10-30.
Release notes
Package name: @types/node
  • 16.18.3 - 2022-10-30
  • 16.18.2 - 2022-10-26
  • 16.18.1 - 2022-10-26
  • 16.18.0 - 2022-10-23
  • 16.11.68 - 2022-10-18
  • 16.11.67 - 2022-10-18
  • 16.11.66 - 2022-10-15
  • 16.11.65 - 2022-10-10
  • 16.11.64 - 2022-10-03
  • 16.11.63 - 2022-10-02
  • 16.11.62 - 2022-09-26
  • 16.11.61 - 2022-09-26
  • 16.11.60 - 2022-09-23
  • 16.11.59 - 2022-09-13
  • 16.11.58 - 2022-09-07
  • 16.11.57 - 2022-09-05
  • 16.11.56 - 2022-08-24
from @types/node GitHub release notes

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:

🧐 View latest project report

👩‍💻 Set who automatically gets assigned

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@lawwman

lawwman commented Dec 29, 2022

Copy link
Copy Markdown
Contributor

@phanshiyu we should at least tie down the node version within package.json before allowing this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants