-
Notifications
You must be signed in to change notification settings - Fork 11.1k
Commit
* Updated to use new release of cron-expression * fix test
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,7 +22,7 @@ | |
"erusev/parsedown": "~1.6", | ||
"league/flysystem": "~1.0", | ||
"monolog/monolog": "~1.12", | ||
"mtdowling/cron-expression": "~1.0", | ||
"dragonmantank/cron-expression": "~2.0", | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
dragonmantank
Author
Contributor
|
||
"nesbot/carbon": "~1.20", | ||
"psr/container": "~1.0", | ||
"psr/simple-cache": "^1.0", | ||
|
2 comments
on commit 07d160a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You forgot to update the other composer.json file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR incomming.
@dragonmantank @taylorotwell This upgrade broke quite a few of our crons, and the breaking change was not documented in the upgrade guide.
Valid cron expressions such as
'2,17,35,47 5-7,11-13 * * *'
(those with both ranges and fields) failed with an error that they could not be parsed. But worse, expressions such as'* * * * MON-FRI'
, silently failed to run at all (the now only supported format is'* * * * 1-5'
). This left our company with several important crons that we were unaware weren't running for most of the day.Here's the outstanding issue: dragonmantank/cron-expression#5