search

wilsto / smartNews

0 stars 0 forks source link

An in-range update of console-stamp is breaking the build 🚨 #39

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency console-stamp was updated from 0.2.6 to 0.2.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

console-stamp is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/wilsto/smartNews/builds/434621020?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 2 commits.

  • aeb14d5 0.2.7
  • ab83a19 As of node version 10.0.0 the console.assert implementation is spec compliant and does not throw anymore. We now handle the failing assert and prevent it from do internal calls to warn. This fixes #29

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

After pinning to 0.2.6 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.