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

[greenkeeper[bot]]

Version 13.0.0 of should just got published.

Branch	Build failing 🚨
Dependency	should
Current Version	12.0.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 failed [Details](https://travis-ci.org/Kikobeats/is-emoji-keyword/builds/272075207?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 11 commits.

• b9bf8ff Release 13.0.0
• c8a5851 Remove ignored file
• ebfdd19 Travis uses node 8
• 92d0db1 Remove bower, as it seems nobody uses it
• fe1ae5c Fix shouldjs/should.js#150
• c4924be Fix build and restore old files. In a bit silly way, but it works.
• c946259 Fix tests
• 90bf91e Prettier everything
• 999b122 Add first version of TS typings for should.js
• 06062c5 Reorganize build
• c50e66a Disable package-lock.json because i am controlling all dependencies

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 Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 12.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.