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

[greenkeeper]

The dependency bcrypt was updated from 3.0.6 to 3.0.7.

🚨 View failing branch.

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, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
• ❌ SockRPG: Build is running (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v3.0.7

bcrypt 3.0.7

Commits

The new version differs by 5 commits.

• 4d3a977 v3.0.7
• a0025da Update dependencies
• bbf0099 Add NodeJS 12 to CI
• c0e9e36 Update nan & node-pre-gyp (#743)
• 4ed9900 Update nan & node-pre-gyp

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[greenkeeper]

• The dependency bcrypt was updated from 3.0.7 to 3.0.8.

Your tests are still failing with this version. Compare changes

Release Notes for v3.0.8

• Update node-pre-gyp to 0.14
• Pre-built binaries for NodeJS 13

Commits

The new version differs by 11 commits.

• 5dd9f07 v3.0.8
• a8ffc8f Update readme to indicate truncation at 72 bytes.
• 081fb70 Fixed up some confusing language.
• f7034f2 GH-720 - change to strcmp.
• e817d25 GH-720 - Update readme regarding timing attacks.
• ae0b145 Update nan to 0.14.0
• bffa114 Merge pull request #763 from anderslatif/master
• 2eabaf2 Add NodeJS 13 to CI (#762)
• 39057dd Changed the word used in the documentation from response to result
• 4bee1a8 Updated the examples to use the word response instead of res to avoid collision
• f6bd1cd Add NodeJS 13 to CI

See the full diff