chore(deps): update dependency node-cron to v4.4.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
node-cron	4.2.1 → 4.4.1

---

Release Notes

merencia/node-cron (node-cron)

v4.4.1

Compare Source

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.

v4.4.0

Compare Source

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.

v4.3.0

Compare Source

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.
  unsupported TypeScript syntax, missing file) instead of an opaque timeout, and
  a failed or timed-out start no longer leaves an orphaned daemon running.
  ([#​484])
• Long-timer drift no longer produces spurious "missed execution" warnings or
  skipped runs on daily/weekly schedules. ([#​485])

Changed

• Minimum supported Node.js is now >= 20 (was >= 20.11); tested on Node
  20, 22 and 24.

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.

---

Configuration

📅 Schedule: (UTC)

• 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.