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

## Version **11.2.1** of [should](https://github.com/shouldjs/should.js) just got published.

Branch


Build failing 🚨




Dependency


should




Current Version


11.2.0




Type


devDependency

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

As should 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 could not complete due to an error [Details](https://travis-ci.org/juliangruber/node-leveled/builds/209292825)

Commits

The new version differs by 1 commits .

• 52b984f Fix .match(RegExp) for everything not supported

See the full diff.

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](https://greenkeeper.io) Bot :palm_tree: