fix(deps)!: update dependency cron to v3 #1461
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.4.3
->3.1.3
Release Notes
kelektiv/node-cron (cron)
v3.1.3
Compare Source
π Bug Fixes
βοΈ Continuous Integrations
v3.1.2
Compare Source
π Builds
β»οΈ Chores
v3.1.1
Compare Source
π Bug Fixes
π Documentation
v3.1.0
Compare Source
β¨ Features
π¨ Tests
β»οΈ Chores
v3.0.0
Compare Source
β Breaking changes
utcOffset
parameter no longer accepts a stringutcOffset
values between -60 and 60 are no longertreated as hours
timeZone
andutcOffset
parametersnow throws an error
cron.job()
method in favor ofnew CronJob(...args)
/CronJob.from(argsObject)
cron.time()
method in favor ofnew CronTime()
CronJob
: constructor no longer accepts an object as its first andonly params. Use
CronJob.from(argsObject)
instead.CronJob
: callbacks are now called in the order they were registered⨠Features
π Bug Fixes
π¦ Code Refactoring
π Documentation
π¨ Tests
β»οΈ Chores
π Styles
v2.4.4
Compare Source
π Bug Fixes
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
dependency upgrade (major)
Does this PR introduce a breaking change?
Other information
β Breaking changes from
cron
impacting@nestjs/schedule
usersOverview
utcOffset
parameter no longer accepts a string (#β699)utcOffset
values between -60 and 60 are no longer treated as hours (#β699)timeZone
andutcOffset
parameters now throws an error (#β699)nextDates
now returns an empty array when called without argument (#β519)Squash commit footer