@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.4.3 to 4.4.4
1 release in betweenevery note read
Release by release
- New
Add support for setting TTL (time-to-live) defaults at the task level and globally in trigger.config.ts, with per-trigger overrides still taking precedence
- New
Large run outputs can use the new API which allows switching object storage providers.
- New
Add platform notifications support to the CLI. The
trigger devandtrigger logincommands now fetch and display platform notifications (info, warn, error, success) from the server. Includes discovery-based filtering to conditionally show notifications based on project file patterns, color markup rendering for styled terminal output, and a non-blocking display flow with a spinner fallback for slow fetches. Use--skip-platform-notificationsflag withtrigger devto disable the notification check. - New
Add
get_span_detailsMCP tool for inspecting individual spans within a run trace.
- New
7 other lines we could not sort, mostly version bumps
- 4.4.4
Multi-provider object storage with protocol-based routing for zero-downtime migration
- 4.4.4
Reduce run start latency by skipping the intermediate queue when concurrency is available. This optimization is rolled out per-region and enabled automatically for development environments.
- 4.4.4
Extended the search filter on the environment variables page to match on environment type (production, staging, development, preview) and branch name, not just variable name and value.
- 4.4.4
Set
application_nameon Prisma connections from SERVICE_NAME so DB load can be attributed by service - 4.4.4
Concurrency-keyed queues now use a single master queue entry per base queue instead of one entry per key. Prevents high-CK-count tenants from consuming the entire parentQueueLimit window and starving other tenants on the same shard.
- 4.4.4
Reduce lock contention when processing large
batchTriggerAndWaitbatches. Previously, each batch item acquired a Redis lock on the parent run to insert aTaskRunWaitpointrow, causingLockAcquisitionTimeoutErrorwith high concurrency (880 errors/24h in prod). SinceblockRunWithCreatedBatchalready transitions the parent toEXECUTING_WITH_WAITPOINTSbefore items are processed, the per-item lock is unnecessary. The newblockRunWithWaitpointLocklessmethod performs only the idempotent CTE insert without acquiring the lock. - 4.4.4
Strip
securequery parameter from QUERY_CLICKHOUSE_URL before passing to ClickHouse client. This was already done for the main and logs ClickHouse clients but was missing for the query client, causing a startup crash withError: Unknown URL parameters: secure.
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.