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 pino from 5.16.0 to 5.17.0 #17

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade pino from 5.16.0 to 5.17.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 2020-02-28.
Release notes
Package name: pino
  • 5.17.0 - 2020-02-28
    • Fix two broken links in the documentation (#769)
    • api.md - fix wrong letter case (#770)
    • Fixed stream metadata loss during prettification (#780)
    • Deprecate the changeLevelName option and alias it to levelKey (#772)
    • Bind pino instance to prettifier (#721)
  • 5.16.0 - 2020-01-11
    • add nestedKey option #759
from pino GitHub release notes
Commit messages
Package name: pino
  • c4fbfdb Bumped v5.17.0
  • 092eb8b Bind pino instance to prettifier (#721)
  • 72eb875 Deprecate the `changeLevelName` option and alias it to `levelKey` (#772)
  • 8ab8595 Fixed stream metadata loss during prettification (#780)
  • d237668 api.md - fix wrong letter case (#770)
  • 6c2de4a Fix two broken links in the documentation (#769)

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

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

1 participant