Releases: Hexagon/croner
8.1.1
8.1.1-dev.0
Changes
- fix(pattern): Fix issue #254, nextRuns returning wrong values when using 4th day of the Month
Full Changelog: 8.1.0...8.1.1-dev.0
8.1.0
8.1.0
- fix(core): Fixes issue #247 (interval setting does seem to ignore startAt) reported by @CommanderStorm through pull requests #248. #249 and #250 by @buzzinJohnnyBoi
- Dev dependency updates
The minor version is bumped to reflect a change more substantial than a typical patch, as the behavior when using the startAt
option in combination with interval
has been changed (corrected).
Full Changelog: 8.0.2...8.1.0
8.0.3-dev.2
What's Changed
- Fix problem caused by #248 and #249 by @buzzinJohnnyBoi in #250
Full Changelog: 8.0.3-dev.1...8.0.3-dev.2
8.0.3-dev.1
What's Changed
- Fix problem caused by PR #248 - startAt set in future with interval by @buzzinJohnnyBoi in #249
Full Changelog: 8.0.3-dev.0...8.0.3-dev.1
8.0.3-dev.0
Development release connected to #247
- Proposed fix for #247
- Dependency updates (eslint 8->9)
- Typo fix
New Contributors
- @buzzinJohnnyBoi made their first contribution in #248
Full Changelog: 8.0.2...8.0.3-dev.0
8.0.2
8.0.1
8.0.1-dev.0
Pre-release 8.0.1-dev.0
8.0.0
Croner 8.0.0
Changes
-
Dropping support for Node.js prior to
18.0
: A major change in this release is the discontinuation of support for Node.js versions prior to18.0
. Ensure that your environment is updated to Node.js18.0
or higher before upgrading to version 8.x. If your project is still using Node.js version16
or lower, we recommend staying with version7.x
of Croner. -
No Significant API Changes: Version 8.x maintains the API functionality of 7.x. There have been no significant changes in the API, allowing for a seamless transition.
-
Preparing for the future: The move to require Node.js
18.0
or higher is an important step towards modernizing our codebase. Dropping support for older Node.js versions allows us to phase out legacy methods and practices that have been a blocker to adopting recent coding standards.
Bugfixes
- fix(core): Fixes an issue with AKDT timezones not triggering. Resolves issue #225
Full Changelog: 7.0.5...8.0.0