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

[greenkeeper[bot]]

Version 1.2.13 of which just got published.

Branch	Build failing 🚨
Dependency	which
Current Version	1.2.12
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

- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/declandewet/common-tags/builds/214126858) - ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/declandewet/common-tags/build/296) - ❌ **bitHound - Dependencies** 3 failing dependencies. [Details](https://www.bithound.io/github/declandewet/common-tags/2706ddf38c4ececb835f85fb555f5f21574a8df0/dependencies/npm#filter-failing-dep) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/declandewet/common-tags/2706ddf38c4ececb835f85fb555f5f21574a8df0/files?status=passing)

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

Version 1.2.14 just got published.

Your tests are still failing with this version. Compare the changes 🚨

[greenkeeper[bot]]

Version 1.3.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨