@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
4.8.8 is the newest release of 4.x.
In short
4 new1 changed
Release note
trigger.dev v4.5.14
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.5.14
Release notes
Read the full release notes: trigger.dev/changelog/v4-5-14
Improvements
Native build server deploys now show a single updating build log line by default; pass
--build-logs fullto stream every line (always used in CI and when output is not a terminal).Realtime stream subscriptions can now refresh an expired access token and reconnect, via a new optional
refreshAccessTokenoption on the client configuration and the React hooks.Subscribe to a realtime stream from its latest record instead of replaying the whole history. Pass
from: "latest"touseRealtimeStream,streams.read(), orfetchStreamto start at the current tail (the latest record, then live updates) instead of replaying (a live "last value" view), andmaxPartsto keep the accumulatedpartsarray bounded. A reconnect or remount resumes from the last record it saw, so no records are missed and none are replayed.from: "latest"needs a server that supports it; older servers safely fall back to a full replay.useRealtimeStreamalso gains alastEventIdoption and returns thelastEventIdof the last part seen, so you can persist the cursor (for example across a page reload) and resume exactly where you left off. AnonPartscallback delivers each throttled batch of parts with their event ids.const { parts, lastEventId } = useRealtimeStream<Frame>(runId, "frames", { from: "latest", // skip history, start at the current tail maxParts: 1, // keep only the most recent frame lastEventId: savedCursor, // resume from a persisted cursor onParts: (batch) => save(batch.at(-1)?.id), // track the cursor accessToken, });Added a
useSessionStreamReact hook for reading a session's output or input channel in realtime. It accumulates records with automatic resume from the last record you received, and supportsfrom: "latest"(start at the current tail, only new records after you connect),maxRecords(keep a bounded number of records in memory), alastEventIdresume cursor, and anonRecordscallback that delivers each throttled batch of records with their event ids.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Task retries that wait in the queue no longer count against the queue's internal redelivery limit, so runs with many long-delay retries are not wrongly failed with TASK_RUN_DEQUEUED_MAX_RETRIES.
All packages: v4.5.14
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
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.