Version bump to 4.3.0 (minor: additive features + fixes, no breaking changes). Notes below are ready to paste into the GitHub release.

node-cron 4.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). (feat: support L (last day of month) #396, closes Please add support for L for day #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. (fix: tolerate late heartbeats so drifting timers don't skip executions #534, closes Opt out "Possible blocking IO or high CPU user..." check #485)
• startTimeout option for background tasks (ms, default 5000). (fix: surface real background task start errors and stop orphaned daemons #535)

Fixes

• Rewrote getNextMatch for correctness around DST: no more ~1-year overshoot when a daily time falls in the spring-forward gap. (refactor: rewrite matcher-walker to infer next run from cron fields #533, closes getNextMatch overshoots ~1 year for a daily schedule whose 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/timed-out start no longer leaves an orphaned daemon running. (fix: surface real background task start errors and stop orphaned daemons #535, closes Problem executing a background task using typescript ? #484)
• Long-timer drift no longer produces spurious "missed execution" warnings / skipped runs on daily/weekly schedules. (fix: tolerate late heartbeats so drifting timers don't skip executions #534, closes Opt out "Possible blocking IO or high CPU user..." check #485)

Compatibility

• Supported Node.js is now >= 20 (was >= 20.11), tested on Node 20, 22 and 24. (chore: support Node.js >= 20 (not just 20.11) and test it in CI #538)

Docs

• README refreshed for v4; API reference documents getTasks/getTask. (docs: refresh README for v4 #536, site)

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.