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

[greenkeeper[bot]]

Version 6.26.0 of babel-register just got published.

Branch	Build failing 🚨
Dependency	babel-register
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-register 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

- ✅ **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/272887) - ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/latticework/jali/branches/greenkeeper-babel-register-6-26-0/builds/1) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/latticework/jali/a949c7dc66b5c3df811782a360fe074758c41da9/files?status=passing) - ❌ **bitHound - Dependencies** 10 failing dependencies. [Details](https://www.bithound.io/github/latticework/jali/a949c7dc66b5c3df811782a360fe074758c41da9/dependencies/npm#filter-failing-dep)

---

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.