An in-range update of c8 is breaking the build 🚨

[greenkeeper[bot]]

The devDependency c8 was updated from 4.1.1 to 4.1.2.

🚨 View failing branch.

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

c8 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/Kronos-Integration/test-step/builds/527552517?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 2 commits.

• 72bf019 chore(release): 4.1.2
• 44d2185 fix: make tmp directory regardless of clean

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]]

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

[greenkeeper[bot]]

• The devDependency c8 was updated from 4.1.2 to 4.1.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• d0b132e chore(release): 4.1.3
• 206b83f fix: switch to mkdirp for Node 8

See the full diff

[greenkeeper[bot]]

• The devDependency c8 was updated from 4.1.3 to 4.1.4.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 6b93355 chore(release): 4.1.4
• fb02ed6 fix: we were not exiting with 1 if mkdir failed (#89)

See the full diff