Skip to content
This repository was archived by the owner on Feb 19, 2021. It is now read-only.
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

@greenkeeper

Description

@greenkeeper

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.0
Commits

The new version differs by 11 commits (ahead by 11, behind by 1).

  • 7ba9094 Bumped v4.1.0.
  • 8a6e24f Updated devDependencies.
  • 0cba928 Merge pull request #211 from pinojs/refactor
  • 79a5671 Merge pull request #201 from joeyvandijk/patch-1
  • f5da9ea Refactor pino to not use new
  • 9987d5a Use Object.create to define Pino prototype (fix #209)
  • 4b3eb2c 4.0.3
  • bb2aa9f adjust naming to reflect separation between bin & pretty.js
  • 172a145 fixed correct remove of require-check
  • 913abdf remove check as requested by davidmarkclements
  • 9826cfb separate CLI features for pretty.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 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions