An in-range update of node-cron is breaking the build 🚨

[greenkeeper]

The dependency node-cron 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.

node-cron 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).

---

Commits

The new version differs by 18 commits.

• f451a8d v2.0.2
• db47539 Merge pull request #116 from node-cron/fix-double-execution
• 610e588 removing file
• 8be224c fix tests
• 79870fb travis
• 64f5958 fix double execution in same second
• 0f52f9c fix travis script
• 1ebdcd1 added nyc to dev dependencies
• 91656c2 fix coveralls
• 48a2b2c fix build script
• c9c9822 update package-lock.json
• 1c572bd Merge pull request #97 from opencollective/opencollective
• ab7dccb Update package.json
• e09c812 Update package.json
• fb27a32 Merge branch 'master' into opencollective

There are 18 commits in total.

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 2.0.1 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

• The dependency node-cron was updated from 2.0.2 to 2.0.3.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀