An in-range update of mongoose-unique-validator is breaking the build 🚨

[Greenkeeper]

The dependency mongoose-unique-validator was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

mongoose-unique-validator 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/travis-ci/push: The Travis CI build could not complete due to an error (Details).
• ❌ ci/circleci: Your tests failed on CircleCI (Details).
• ✅ coverage/coveralls: First build on greenkeeper/mongoose-unique-validator-2.0.2 at 0.0% (Details).

---

Commits

The new version differs by 2 commits.

• 1cc09b1 Marking as 2.0.2
• 785fa2f changed .count to .countDocuments. Because .count is deprecated and will be removed in future versions. And it's raising flags when being used. (#84)

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]

• The dependency mongoose-unique-validator was updated from 2.0.2 to 2.0.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

• da52b0c Marking as 2.0.3
• 869f90a Updates dependencies
• 9ac4a4c Fixes minor typos in comment, test
• c5d1c6e Escapes RegExp chars (#95)
• 08da631 Limit files in npm package [ci skip]

See the full diff