This repository was archived by the owner on Feb 19, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
This repository was archived by the owner on Feb 19, 2021. It is now read-only.
An in-range update of pino is breaking the build 🚨 #14
Copy link
Copy link
Open
Labels
Description
Version 4.1.0 of pino just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | pino |
| Current Version | 4.0.3 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As pino is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes
v4.1.0Commits
The new version differs by 11 commits (ahead by 11, behind by 1).
7ba9094Bumped v4.1.0.8a6e24fUpdated devDependencies.0cba928Merge pull request #211 from pinojs/refactor79a5671Merge pull request #201 from joeyvandijk/patch-1f5da9eaRefactor pino to not usenew9987d5aUse Object.create to define Pino prototype (fix #209)4b3eb2c4.0.3bb2aa9fadjust naming to reflect separation between bin & pretty.js172a145fixed correct remove of require-check913abdfremove check as requested by davidmarkclements9826cfbseparate CLI features forpretty.js(bin.js) with default features (pretty.js), to be able to use webpack with Node.js code in AWS Lambda environments
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Reactions are currently unavailable