This repository has been archived by the owner on Aug 25, 2024. It is now read-only.
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:
^7.0.1
->^8.0.0
Release Notes
hexagon/croner (croner)
v8.1.0
Compare Source
8.1.0
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 withinterval
has been changed (corrected).Full Changelog: Hexagon/croner@8.0.2...8.1.0
v8.0.2
Compare Source
Changes
Full Changelog: Hexagon/croner@8.0.1...8.0.2
v8.0.1
Compare Source
Croner 8.0.1
Full Changelog: Hexagon/croner@8.0.0...8.0.1
v8.0.0
Compare Source
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
Full Changelog: Hexagon/croner@7.0.5...8.0.0
v7.0.7
Compare Source
v7.0.6
Compare Source
v7.0.5
Compare Source
Changes
Full Changelog: Hexagon/croner@7.0.4...7.0.5
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.