Open greenkeeper[bot] opened 6 years ago
After pinning to 1.2.5 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
dependency
node-schedule was updated from 1.3.0
to 1.3.1
.Your tests are still failing with this version. Compare changes
The new version differs by 7 commits.
c7f8827
Version 1.3.1
82aa564
src: avoid discarding the tz parameter
3ce9b06
deps: upgrade to cron-parser@^2.7.3
5d3777e
src: make sure Invocation fireDate is a CronDate
a6430fc
fixed reschedule and plural of information
0754b0d
doc: touch up a typo
be9e6d8
doc: add valid values for RecurrenceRule props
See the full diff
dependency
node-schedule was updated from 1.3.1
to 1.3.2
.Your tests are still failing with this version. Compare changes
Version 1.3.0 of node-schedule was just published.
This version is covered by your current version range and after updating it in your project the build failed.
node-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
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/sebastianhaas/medical-appointment-scheduling-server/builds/326285921?utm_source=github_status&utm_medium=notification)Commits
The new version differs by 4 commits.
03c8ddf
Version 1.3.0
28fa70a
src: make sure the job runs on the exact date
fa40d67
doc: fix cron string diagram consistency
eabb2f3
src: pass fire date when job gets invoked
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: