An in-range update of babel-cli is breaking the build 🚨

[greenkeeper[bot]]

Version 6.26.0 of babel-cli just got published.

Branch	Build failing 🚨
Dependency	babel-cli
Current Version	6.24.1
Type	devDependency

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

As babel-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details

- ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/phenomnomnominal/tractor-plugin-visual-regression/f92c268f3546af192f4bf73ef8b527a7f61194be/files?status=passing) - ❌ **bitHound - Dependencies** 2 failing dependencies. [Details](https://www.bithound.io/github/phenomnomnominal/tractor-plugin-visual-regression/f92c268f3546af192f4bf73ef8b527a7f61194be/dependencies/npm#filter-failing-dep) - ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/phenomnomnominal/tractor-plugin-visual-regression/builds/265386552?utm_source=github_status&utm_medium=notification) - ✅ **coverage/coveralls** First build on greenkeeper/babel-cli-6.26.0 at 34.746% [Details](https://coveralls.io/builds/12869932)

---

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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