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

[greenkeeper]

Version 11.2.0 of should just got published.

Branch	Build failing 🚨
Dependency	should
Current Version	11.1.2
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 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details

• ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 7 commits .

• 64ad890 Merge branch 'master' of github.com:shouldjs/should.js
• 48fac91 Release 11.2.0
• 51a3c5e Add .only modifier for .keys
• f1f3d5a Merge pull request #131 from jakearchibald/patch-1
• 0fd9c34 Minor grammar correction
• d2cd6cc Remove very old browsers from testing list
• 77be237 Updated build

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 11.2.1 just got published.

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

Commits

The new version differs by 1 commits .

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

See the full diff.