fix(deps): update dependency croner to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
croner (source)	^7.0.1 -> ^8.0.0

---

Release Notes

hexagon/croner (croner)

v8.1.1

Compare Source

Changes

• fix(pattern): Fixes issue #​254, nextRuns returning wrong values when using 4th day of the Month

Full Changelog: Hexagon/croner@8.1.0...8.1.1

v8.1.0

Compare Source

8.1.0

• fix(core): Fixes issue #​247 (interval setting does seem to ignore startAt) reported by @​CommanderStorm through pull requests https://github.com/Hexagon/croner/pull/248. https://github.com/Hexagon/croner/pull/249 and https://github.com/Hexagon/croner/pull/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: Hexagon/croner@8.0.2...8.1.0

v8.0.2

Compare Source

Changes

• Fix #​245; using utcOffset together with a once-trigger throws error: Invalid time zone specified.
• Update pattern.js by @​mceachen in https://github.com/Hexagon/croner/pull/241

Full Changelog: Hexagon/croner@8.0.1...8.0.2

v8.0.1

Compare Source

Croner 8.0.1

• fix(core): Add safeguard for out of control loop on internal error.
• chore(docs): s/wether/whether by @​mceachen in https://github.com/Hexagon/croner/pull/233

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 to 18.0. Ensure that your environment is updated to Node.js 18.0 or higher before upgrading to version 8.x. If your project is still using Node.js version 16 or lower, we recommend staying with version 7.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: Hexagon/croner@7.0.5...8.0.0

v7.0.8

Compare Source

v7.0.7

Compare Source

v7.0.6

Compare Source

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d4fc690

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR