An in-range update of why-is-node-running is breaking the build 🚨

greenkeeper[bot] commented 4 years ago

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency why-is-node-running was updated from `2.1.0` to `2.1.1`.

🚨 View failing branch.

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

why-is-node-running 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

- ✅ **security/gitguardian:** GitGuardian did not find any leak. ([Details](https://app.gitguardian.com)). - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/gerard2p/koaton/builds/659326181?utm_source=github_status&utm_medium=notification)).

Commits

The new version differs by 2 commits.

2d83bde 2.1.1
010cdb1 Exclude unrefed timers

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 4 years ago

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

greenkeeper[bot] commented 4 years ago

The dependency why-is-node-running was updated from 2.1.1 to 2.1.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

d1299a9 2.1.2
ed00a7a Update readme to include notes regarding the support for unrefed timers
b73542b Fix issue with excluding unrefed timers in node version <v11.0.0

See the full diff

gerard2perez / koaton