An in-range update of nest-schedule is breaking the build 🚨

[greenkeeper]

The dependency nest-schedule was updated from 0.6.0 to 0.6.1.

🚨 View failing branch.

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

nest-schedule 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

• ✅ ci/circleci: Your tests passed on CircleCI! (Details).
• ✅ codecov/project: No report found to compare against (Details).
• ✅ codecov/patch: Coverage not affected. (Details).
• ✅ Better Code Hub: ✅ Better Code Hub approves this code (Details).
• ❌ WhiteSource Security Check: The Security Check found 3 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
High	8.0	WS-2019-0064	#433
Medium	5.0	WS-2019-0047	#418
Medium	5.0	WS-2019-0019	#136

Scan token: 0322dc6dafa34a028f7aa2d797fbbb79

---

Commits

The new version differs by 7 commits.

• 20e0b42 use nestjs logger instead, remove logger option
• bce37ff Delete Schedule.ts
• b29c556 Merge pull request #28 from sandeepsuvit/hotfix/dynamic-cron-job
• bde88e7 Fixes for dynamic cron job issue while running the application - startTime is undefined
• e85068f fix readme
• 8413c77 fix readme add key parameter to decorators
• cc0fa72 completed doc

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 nest-schedule was updated from 0.6.1 to 0.6.2.

Your tests are still failing with this version. Compare changes

Release Notes for v0.6.2

1. Remove logger option, use NestJS internal logger instead
2. Bug fixes

Commits

The new version differs by commits.

See the full diff