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

[greenkeeper]

Version 1.0.3 of bcrypt just got published.

Branch	Build failing 🚨
Dependency	bcrypt
Current Version	1.0.2
Type	dependency

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

bcrypt is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ❌ coverage/coveralls First build on greenkeeper/bcrypt-1.0.3 at 84.456% Details

---

Commits

The new version differs by 7 commits.

• 054cf76 Version bump.
• af5f8c4 use npm scripts instead of node-gyp directly.
• f5eb5d1 Merge pull request #499 from agathver/documentation
• a04c269 Update README to include links to new wiki page
• 45f498e Merge pull request #527 from Agathver/node8_fix
• be906fc Make compatible with Node 8
• cb82c05 add node v7 to appveyor config

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]

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