Bump dragonmantank/cron-expression from 2.3.0 to 3.0.0

[dependabot-preview]

Bumps dragonmantank/cron-expression from 2.3.0 to 3.0.0.

Release notes

Sourced from dragonmantank/cron-expression's releases.

v3.0.0

MAJOR CHANGE - In previous versions of this library, setting both a "Day of Month" and a "Day of Week" would be interpreted as an AND statement, not an OR statement. For example:

30 0 1 * 1

would evaluate to "Run 30 minutes after the 0 hour when the Day Of Month is 1 AND a Monday" instead of "Run 30 minutes after the 0 hour on Day Of Month 1 OR a Monday", where the latter is more inline with most cron systems. This means that if your cron expression has both of these fields set, you may see your expression fire more often starting with v3.0.0.

Added

• Additional docblocks for IDE and documentation
• Added phpstan as a development dependency
• Added a Cron\FieldFactoryInterface to make migrations easier (#38)

Changed

• Changed some DI testing during TravisCI runs
• \Cron\CronExpression::determineTimezone() now checks for \DateTimeInterface instead of just \DateTime
• Errors with fields now report a more human-understandable error and are 1-based instead of 0-based
• Better support for \DateTimeImmutable across the library by typehinting for \DateTimeInterface now
• Literals should now be less case-sensative across the board
• Changed logic for when both a Day of Week and a Day of Month are supplied to now be an OR statement, not an AND

Fixed

• Fixed infinite loop when determining last day of week from literals
• Fixed bug where single number ranges were allowed (ex: 1/10)
• Fixed nullable FieldFactory in CronExpression where no factory could be supplied
• Fixed issue where logic for dropping seconds to 0 could lead to a timezone change

Changelog

Sourced from dragonmantank/cron-expression's changelog.

[3.0.0] - 2020-03-25

MAJOR CHANGE - In previous versions of this library, setting both a "Day of Month" and a "Day of Week" would be interpreted as an AND statement, not an OR statement. For example:

30 0 1 * 1

would evaluate to "Run 30 minutes after the 0 hour when the Day Of Month is 1 AND a Monday" instead of "Run 30 minutes after the 0 hour on Day Of Month 1 OR a Monday", where the latter is more inline with most cron systems. This means that if your cron expression has both of these fields set, you may see your expression fire more often starting with v3.0.0.

Added

• Additional docblocks for IDE and documentation
• Added phpstan as a development dependency
• Added a Cron\FieldFactoryInterface to make migrations easier (#38)

Changed

• Changed some DI testing during TravisCI runs
• \Cron\CronExpression::determineTimezone() now checks for \DateTimeInterface instead of just \DateTime
• Errors with fields now report a more human-understandable error and are 1-based instead of 0-based
• Better support for \DateTimeImmutable across the library by typehinting for \DateTimeInterface now
• Literals should now be less case-sensative across the board
• Changed logic for when both a Day of Week and a Day of Month are supplied to now be an OR statement, not an AND

Fixed

• Fixed infinite loop when determining last day of week from literals
• Fixed bug where single number ranges were allowed (ex: 1/10)
• Fixed nullable FieldFactory in CronExpression where no factory could be supplied
• Fixed issue where logic for dropping seconds to 0 could lead to a timezone change

Commits

• 70c187e StyleCI fixes
• 90efed9 Added CHANGELOG entry for #38
• 5e2fce6 Expanded tests for casing
• 2815ad8 Added regression test and cleaned up some ?CHANGELOG language
• 86abbda Updated changelog for 2.4.0
• d4307f1 Merge pull request #37 from holtkamp/patch-use-null-coalescing-operator
• 07ca402 Merge pull request #38 from holtkamp/patch-use-FieldFactoryInterface
• b55e1f8 Merge pull request #61 from dragonmantank/issue/35-fix-and-or-problem
• 1942ec1 Actually use FieldFactoryInterface
• 33e9c65 Sync with master
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will not automatically merge this PR because it includes an out-of-range update to a production dependency.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)