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 winston from 3.10.0 to 3.11.0 #272

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

empierre
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade winston from 3.10.0 to 3.11.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 1 version ahead of your current version.
  • The recommended version was released 22 days ago, on 2023-10-07.
Release notes
Package name: winston from winston GitHub release notes
Commit messages
Package name: winston
  • 1c8c65f 3.11.0
  • 37f4282 Bump split2 from 4.1.0 to 4.2.0 (#2336)
  • fdcc893 Bump actions/checkout from 3 to 4 (#2346)
  • dcbec34 Bump @ colors/colors packgae to 1.6.0 (#2353)
  • aaaa4c0 Bump rimraf from 3.0.2 to 5.0.5 (#2357)
  • 914b846 feat: add guardrails to the instantiation of a Profiler (#2226)
  • 23cb80c Bump @ types/node from 20.3.1 to 20.4.2 (#2329)
  • 1c43f7b Bug Fix: FileTransportOptions type missing lazy:boolean option (#2334)

Compare


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

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@empierre empierre merged commit d6e9c1d into nodejs Nov 2, 2023
3 checks passed
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