@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.5.4 to 4.5.5
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 3
- new
- 3
- fixes
Before you upgrade
Tick each one off as you go- Breaking4.5.5
Release by release
- Breaking
Remove the deprecated realtime stream write endpoint used by retired v3 task clients.
- New
Add experimental Node.js 24 and 26 task runtimes. Set
runtimetoexperimental-node-24orexperimental-node-26intrigger.config.ts. - New
Add
defaultRegionto the project GET and list API responses; null when unset. - New
Speed up idempotency checks on
batchTriggercalls that use idempotency keys. Large batches against a task with a big run history no longer degrade to multi-second lookups. - Fixed
Fix batchTrigger requests that set a per-item idempotency key failing with an error instead of creating and deduplicating the runs
- Fixed
Avoid opening a redundant database connection pool when the legacy and primary databases are the same server, preventing connection usage from doubling.
- Fixed
Fix pages occasionally loading unstyled or failing to load during a deploy. The dashboard now reloads automatically to recover.
- Breaking
3 other lines we could not sort, mostly version bumps
- 4.5.5
Transient internal sync failures are now retried quietly instead of surfacing as errors.
- 4.5.5
Optionally route ClickHouse read traffic to a read replica while writes stay on the primary. Set
CLICKHOUSE_READER_URLto move all reads, or target the busiest paths withRUNS_LIST_CLICKHOUSE_URL(runs list) andEVENTS_READER_CLICKHOUSE_URL(traces, spans, logs). All optional; unset keeps current behavior. - 4.5.5
The "Preview branches" usage on the Limits page now counts only preview branches.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.