-
Notifications
You must be signed in to change notification settings - Fork 18
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
Upgrade debug to v2.6.9 #13
Comments
Note: That issue is already fixed in v2.6.9 Refs: debug-js/debug#504 |
I am a bit lost. What are you proposing apart from #11? |
Anyway, an anticipated upgrade of debug to v2.6.9 it would be more logic. correct me if wrong. |
v1.0.5: https://unpkg.com/pino-debug@1.0.5/package.json (
|
I’m still lost. What do you want us to do? Is the release on npm not in sync to what is on master? |
yep, basically bump up a new pino-debug release with debug v2.6.9 |
Released v1.0.6. |
👍 |
Actually
pino-debug@1.0.5
usesdebug@2.6.0
, because of this security vulnerability an upgrade of debug to v2.6.9 should fix it.Update: it's already done at b892b08
The text was updated successfully, but these errors were encountered: