An in-range update of glob-fs is breaking the build 🚨

[greenkeeper[bot]]

Version 0.1.7 of glob-fs just got published.

Branch	Build failing 🚨
Dependency	glob-fs
Current Version	0.1.6
Type	devDependency

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

As glob-fs 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/257131) - ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/latticework/jali/branches/greenkeeper-glob-fs-0-1-7/builds/1) - ❌ **bitHound - Dependencies** null [Details](https://www.bithound.io/github/latticework/jali/greenkeeper%2Fglob-fs-0.1.7) - ❌ **bitHound - Code** null [Details](https://www.bithound.io/github/latticework/jali/greenkeeper%2Fglob-fs-0.1.7)

---

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 0.1.6 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.