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

[greenkeeper[bot]]

Version 1.2.12 of which just got published.

Branch	Build failing 🚨
Dependency	which
Current Version	1.2.11
Type	devDependency

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

As which 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/declandewet/common-tags/838ae2cc751fd675f6e6a384465bf0cb93044721/files?status=passing) - ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/declandewet/common-tags/838ae2cc751fd675f6e6a384465bf0cb93044721/dependencies/npm?status=passing) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/declandewet/common-tags/builds/175209341)

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