Bump node-cron from 4.2.1 to 4.4.1

[dependabot]

Bumps node-cron from 4.2.1 to 4.4.1.

Release notes

Sourced from node-cron's releases.

v4.4.1

Patch release.

Changed

• Renamed the distributedTtl task option to distributedLease (same meaning: the safety lease, in ms, for lease-based run coordinators). distributedTtl was the only abbreviation in the options API and shipped just days ago in 4.4.0, so it's removed without an alias. If you adopted distributedTtl from 4.4.0, rename it to distributedLease. (#551)

Full Changelog: node-cron/node-cron@v4.4.0...v4.4.1

v4.4.0

Features

• Distributed run coordination — opt-in distributed: true runs a task on a single instance per fire across a fleet (the #477 use case). Ships a built-in NODE_CRON_RUN env-var default (one designated runner, no dependencies) and a pluggable RunCoordinator (via setRunCoordinator, or the per-task runCoordinator option) for high-availability, per-fire coordination (e.g. a Redis lock). Adds the distributedTtl option and an execution:skipped event carrying a reason ('not-elected' | 'coordinator-error'). Works for inline and background tasks. (#549, closes #477)
• Task introspection on ScheduledTask: getNextRuns(n) (preview the next N run times), match(date), msToNext(), isBusy(), runsLeft() and getPattern(). (#547)
• cron.parse(expression) and cron.validateDetailed(expression) — decompose an expression into its fields, or get every field-level problem (without throwing) for tooling and richer error messages. (#548)

Fixes

• getNextMatch no longer scans every time of day on a day that matches the day-of-month but not the weekday. A dense expression constrained by both (e.g. * * * 15 * 1) could take minutes to resolve; it is now instant. (#542)

Internal

• Cleanups with no public API change: fixed the milisecond → millisecond spelling and the convertion/ → conversion/ directory name. (#543)

Docs

• New Distributed Coordination guide, plus pages for task introspection and parse/validateDetailed, at nodecron.com.

Full Changelog: node-cron/node-cron@v4.3.0...v4.4.0

v4.3.0

Features

• L (last day of month) in the day-of-month field — e.g. 0 0 12 L * *, leap-year aware, and combinable with explicit days (15,L). (#396, closes #147 — thanks @​antonidasyang)
• missedExecutionTolerance option (ms, default 1000): a heartbeat that wakes a little late still runs its slot instead of being reported as missed. Always capped to the gap to the next slot. (#534, closes #485)
• startTimeout option for background tasks (ms, default 5000). (#535)

Fixes

• Rewrote getNextMatch for correctness around DST: no more ~1-year overshoot when a daily time falls in the spring-forward gap. (#533, closes #518)
• Background task start failures now reject with the real cause (e.g. unsupported TypeScript syntax, missing file) instead of an opaque timeout, and a failed/timed-out start no longer leaves an orphaned daemon running. (#535, closes #484)
• Long-timer drift no longer produces spurious "missed execution" warnings / skipped runs on daily/weekly schedules. (#534, closes #485)

Compatibility

• Supported Node.js is now >= 20 (was >= 20.11), tested on Node 20, 22 and 24. (#538)

Docs

• README refreshed for v4; API reference documents getTasks/getTask. (#536, #537)

Behavior note

• missedExecutionTolerance defaults to 1000ms, so a scheduled run that wakes up to ~1s late now executes instead of emitting execution:missed. This is a bug-fix improvement, not an API break.

Full Changelog: node-cron/node-cron@v4.2.1...v4.3.0

Changelog

Sourced from node-cron's changelog.

[4.4.1] - 2026-06-18

Changed

• Renamed the distributedTtl option to distributedLease (same meaning: the safety lease, in ms, for lease-based coordinators). The old name was the only abbreviation in the options API; the new one groups with distributed. distributedTtl was introduced in 4.4.0 and is removed without an alias.

[4.4.0] - 2026-06-17

Added

• Task introspection on ScheduledTask: getNextRuns(n) (preview the next N run times), match(date), msToNext(), isBusy(), runsLeft() and getPattern(). (#547)
• cron.parse(expression) and cron.validateDetailed(expression): decompose an expression into its fields, or get every field-level problem (without throwing) for tooling and richer error messages. (#548)
• Distributed run coordination — opt-in distributed: true runs a task on a single instance per fire across a fleet. Ships a built-in NODE_CRON_RUN env-var default (one designated runner, no dependencies) and a pluggable RunCoordinator (via setRunCoordinator, or the per-task runCoordinator option) for high-availability, per-fire coordination (e.g. a Redis lock). Adds the distributedTtl option and an execution:skipped event carrying a reason ('not-elected' | 'coordinator-error'). Works for inline and background tasks. (#549)

Fixed

• getNextMatch no longer scans every time of day on a day that matches the day-of-month but not the weekday. A dense expression constrained by both (e.g. * * * 15 * 1) could take minutes to resolve; it is now instant.

Changed

• Internal-only cleanups (no public API change): fixed the milisecond → millisecond spelling and the convertion/ → conversion/ directory name.

[4.3.0] - 2026-06-17

Added

• L (last day of month) in the day-of-month field — e.g. 0 0 12 L * *, leap-year aware and combinable with explicit days (15,L). (#147)
• missedExecutionTolerance option (ms, default 1000): a heartbeat that wakes a little late still runs its slot instead of being reported as missed. Always capped to the gap to the next slot, so it can never run a slot twice. (#485)
• startTimeout option for background tasks (ms, default 5000). (#535)

Fixed

• DST correctness in getNextMatch: no more ~1-year overshoot when a daily time falls in the spring-forward gap. (#518)
• Background task start failures now reject with the real cause (e.g.

... (truncated)

Commits

• 3e35f25 chore(release): 4.4.1 (#552)
• 23c7849 refactor!: rename distributedTtl option to distributedLease (#551)
• 49fe016 chore(release): 4.4.0 (#550)
• 2ba12f1 feat: distributed run coordination (one instance per fire across a fleet) (#549)
• 8702f78 test: make the isBusy 'in progress' check deterministic
• cbe36bc feat: add cron.parse and cron.validateDetailed (#548)
• 394e57e feat: task introspection (getNextRuns, match, msToNext, isBusy, runsLeft, get...
• 7bd9e4a docs: add CHANGELOG covering v4.0.0 -> 4.3.0 (#546)
• f3574f9 chore: bump sinon to v22 to drop the deprecated lodash.get transitive dep (#545)
• b5a7aa0 chore: add SECURITY, CONTRIBUTING and issue templates (#544)
• 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 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)