An in-range update of pre-commit is breaking the build 🚨

[greenkeeper[bot]]

Version 1.1.3 of pre-commit just got published.

Branch	Build failing 🚨
Dependency	pre-commit
Current Version	1.1.2
Type	devDependency

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

As pre-commit 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/mongodb-js/mongodb-top/builds/179157552)

Commits

The new version differs by 11 commits .

• 0f0833a [dist] 1.1.3
• fa6119d Merge pull request #57 from blacksonic/master
• 2abd42b Merge pull request #64 from kevinoid/relative-link
• 1a04430 Make pre-commit hook symlink relative
• 2ca2fb9 Merge pull request #60 from saiichihashimoto/patch-1
• b6e63d7 Update README.md
• 4510f45 [fix] add .bashrc to supported home files
• 3f83f72 Merge pull request #54 from fhemberger/fix/dependencies
• 683221f Merge pull request #53 from fhemberger/fix/travis
• 53ec6e9 Update dependencies
• eb7ac24 [travis] Add Node@4.x, use new container infrastructure

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