nhcarrigan/minori
11
0
Fork 0
generated from nhcarrigan/template
Code Issues Pull Requests 9 Actions Releases Activity

deps: update node-cron to 4.3.0 #10

Open
minori wants to merge 1 commits from dependencies/update-node-cron into main
pull from: dependencies/update-node-cron
merge into: nhcarrigan:main
Conversation 0 Commits 1 Files Changed 2
+7 -7
minori commented 2026-06-27 07:07:06 -07:00
Owner
Copy Link
Copy Source

Dependency Update

Updates node-cron from 4.2.1 to 4.3.0.

Type

dependencies

Changelog

Changelog

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: https://github.com/node-cron/node-cron/compare/v4.2.1...v4.3.0

✨ This PR was created by Minori, your friendly dependency updater! 🌸

## Dependency Update Updates **node-cron** from `4.2.1` to `4.3.0`. ### Type dependencies ### Changelog ## Changelog ### 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 `1000`ms, 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**: https://github.com/node-cron/node-cron/compare/v4.2.1...v4.3.0 --- ✨ This PR was created by Minori, your friendly dependency updater! 🌸
minori added 1 commit 2026-06-27 07:07:06 -07:00
deps: update node-cron to 4.3.0
Node.js CI / CI (pull_request) Failing after 50s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m25s
Details
83e0019e26
Some checks are pending
Node.js CI / CI (pull_request) Failing after 50s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m25s
Details
This pull request doesn't have enough required approvals yet. 0 of 1 approvals granted from users or teams on the allowlist.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin dependencies/update-node-cron:dependencies/update-node-cron
git checkout dependencies/update-node-cron
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
hanna (Hanna Rose) hikari (Hikari) ilenia kirsten minori (Minori) naomi (Naomi Carrigan) nerdychara (Anna Cottrill) nick rain somil tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/minori#10
Delete Branch "dependencies/update-node-cron"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?