@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.5.16 to 4.8.8
22 releases in betweenevery note read
- 10
- changes to make
- 0
- advisories fixed
- 142
- new
- 52
- fixes
Before you upgrade
Tick each one off as you go- Breaking4.8.2
- Breaking4.8.2
- Breaking4.7.3
- Breaking4.6.0
- Breaking4.6.0
- Breaking4.6.0
- Deprecated4.8.3
- Deprecated4.7.0
- Deprecated4.7.0
- Deprecated4.6.0
Security
- 4.8.5
Deployed tasks on the
node,node-22,node-24andnode-26runtimes now run on Node.js 22.23.5, 24.22.3 and 26.13.1, the November 2026 security releases. They fix several high severity issues in HTTP/2 and TLS, including CVE-2026-123863, CVE-2026-123864, CVE-2026-123865, CVE-2026-123866, CVE-2026-123872 and CVE-2026-123874, plus CVE-2026-126051 on Node.js 24 and 26. Existing deployments keep the old runtime until you redeploy with this version. - 4.8.2
Upgrade
socket.io-clientto 4.8.4 so projects using the SDK and CLI installws8.21 instead of 8.17.1, which has published advisories (GHSA-96hv-2xvq-fx4p, GHSA-58qx-3vcg-4xpx). The old pin blocked upgradingwswithout a package manager override. - 4.7.7
Deployed tasks on the
node,node-22,node-24andnode-26runtimes now run on Node.js 22.23.4, 24.22.1 and 26.12.1, the October 2026 security releases. They fix CVE-2026-111497 (an out-of-bounds write in the Brotli decoder) and several TLS hostname verification bypasses. Existing deployments keep the old runtime until you redeploy with this version. - 4.7.7
Self-hosted: The webapp and supervisor images now run on Node.js 24.22.1. The supervisor no longer trusts certificates issued under the compromised emSign (eMudhra) certificate authorities, and the webapp image builds its database migration tool with Go 1.26.10, which rejects the compromised eMudhra intermediates.
Release by release
- New
The MCP
list_runstool can now filter runs by queue, batch, schedule and bulk action, and its descriptions now say thatperiodtakes precedence overfromandto. - New
When OIDC token requests are still throttled after retries,
auth.getOIDCToken()now throwsRateLimitErrorwith codeRATE_LIMIT_EXCEEDEDfor both per-run and shared API limits. If you catch these errors withinstanceof OIDCTokenError, check forRateLimitErrorinstead. Other OIDC errors and retry behavior are unchanged. - New
Stop losing a run's suspend when the supervisor's first attempt to hand it off fails unexpectedly.
- New
- New
Sessions and
chat.agentnow accept the object form ofconcurrencyKeyintriggerConfig, giving each concurrency limit its own key, the same astask.trigger(). - Fixed
Fix runs failing with
TASK_DID_CONCURRENT_WAITon their first wait whenprocessKeepAliveis enabled. - Fixed
Fix
chat.agentchannels on AI SDK 7 failing the whole turn when a channel file can't be downloaded. A file the connector owns but can't read is now replaced with an[Attached file "…" could not be loaded]note and the agent still answers, as it does on AI SDK 6. AI SDK 7 describes a file's URL in a tagged form that the SDK didn't recognise, so the failed file was never found. - Fixed
Fix two compaction problems on AI SDK 7. After a compaction, a
chat.agentturn that continued a tool approval sent the model the full pre-compaction transcript instead of the summary, which undid the compaction (this also affectedchat.MessageAccumulator). And between-turn compaction, inchat.agentandchat.createSession, was asked about the whole turn's token usage instead of the last step's, soshouldCompactthresholds triggered too early on multi-step turns. - Fixed
Fix
chat.agentsteering on AI SDK 7. A steering message thatpendingMessages.prepareturns into asystemmessage no longer makes the step fail with an invalid-prompt error:chat.toStreamTextOptions()now setsallowSystemInMessages: true, as AI SDK 5 and 6 already behave (passallowSystemInMessages: falseafter the spread to keep AI SDK 7's strict default). A turn whose stream ends on an error now reportsfinishReason: "error"inonTurnComplete, where it could beundefinedor the previous step's reason. - Fixed
Fix a
chat.agenttool result containing aBigIntfailing the next turn's model call in apps that defineBigInt.prototype.toJSON. It is now sent as the JSON thattoJSONgives, in the next step and in later turns. - Fixed
Fix
chat.agentfailing the next step or turn withAI_InvalidPromptError("The messages do not match the ModelMessage schema") when a tool returned a value that isn't plain JSON, such as aDatefrom an ORM row. On AI SDK 6, and AI SDK 7 before 7.0.101, tool results are now converted to JSON the way newer AI SDK versions do it, so aDatereaches the model as its ISO string. A value JSON can't hold, such as aBigIntor a circular reference, is replaced by an error result that names the tool and the field, and the same error is logged on the run.
- New
- New
Allow an explicit audience when signing and verifying JWTs and user-actor tokens.
- New
Deploys on the
bun-1.4runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster.import.meta.urland__dirnamestill point at your files under/app, so files you read next to your code must be in the image as before (e.g. withadditionalFiles). Setbuild.bunBytecode: falseintrigger.config.tsto turn compilation off. - New
trigger devandtrigger deployno longer crash withspawn ... ENOENTon bun runtimes when Bun isn't installed at~/.bun. The CLI now falls back tobunon yourPATH(Homebrew, mise and similar installs), and if Bun still can't be started,trigger devreports a readable error andtrigger deployskips local skill discovery with a warning and carries on. - New
Bundled task files now keep their project layout (for example
/app/src/trigger/tasks.mjs) when the CLI runs from outside the project, such asnpx trigger.dev deploy. Before, they could land under a path containing the project's location, away from the filesadditionalFilescopies next to them, so reads relative toimport.meta.urlfailed.
- New
- Security
Deployed tasks on the
node,node-22,node-24andnode-26runtimes now run on Node.js 22.23.5, 24.22.3 and 26.13.1, the November 2026 security releases. They fix several high severity issues in HTTP/2 and TLS, including CVE-2026-123863, CVE-2026-123864, CVE-2026-123865, CVE-2026-123866, CVE-2026-123872 and CVE-2026-123874, plus CVE-2026-126051 on Node.js 24 and 26. Existing deployments keep the old runtime until you redeploy with this version.
- Security
- New
Add opt-in AWS session tags with
awsCredentialProvider({ sessionTags: true })for task-level IAM restrictions and attribute-based permissions. Tags come from the verified run identity. Update the role trust policy to allowsts:TagSessionbefore enabling them; existing integrations remain untagged. - New
Logins made with
trigger.dev loginor the MCP server now stop working after 7 days without use. When that happens, the CLI and the MCP server start a new login instead of failing with an auth error, and in CI the CLI says to log in again. Self-hosted instances can change the window withCLI_LOGIN_IDLE_TIMEOUT_DAYS, or set it to0to turn it off for new logins. Logins made before this change aren't affected. - New
Add
infisicalAccessTokenat@trigger.dev/sdk/oidc/infisicalto authenticate tasks with Infisical using OIDC instead of stored credentials. Supports US, EU, and self-hosted instances, custom audiences, and Infisical organization scoping. - New
Deploy from GitHub Actions using Trusted publishing and GitHub OIDC without storing a Trigger.dev API key. These deployments run entirely on the build server and do not grant the CLI access to environment variables.
- New
- Deprecated
Deprecates the legacy Bun runtime.
runtime: "bun"(and its explicit spelling"bun-legacy"), which deploys Bun 1.3.3 with Node.js 20 alongside it, now prints a deprecation warning, and deploys that use it will be rejected from January 5, 2027. Switch toruntime: "bun-1.4"(Bun 1.4.4 on an image with no Node.js binary) and redeploy. - New
CLI and MCP logins are now bound to the machine that started them. Approving a login in your browser sends you back to the CLI automatically, or, when the browser is on another machine, shows a code to paste into the terminal (or pass with
trigger.dev login --code). Older CLI versions will need to upgrade to log in. - New
Add
trigger webhooks set-secretandtrigger webhooks generate-secret, which store a webhook endpoint's signing secret without printing it.set-secretreads the secret from a pipe, an environment variable or a.envfile, andgenerate-secretsaves the new secret to an env file. When the endpoint already has a secret, both ask how long the old one keeps working (or take--previous-secret-ttl 24hin scripts). The MCP server'sset_webhook_secretandgenerate_webhook_secretdescriptions now point AI agents at these commands, so the secret stays out of the agent's context. - New
Add
trigger.refresh(ctx, id)to request an earlier status check for a Convex-tracked run, so applications using Trigger Realtime can publish results without waiting for the next scheduled poll. Requests are coalesced and rate-limited, use the existing completion callback, and retain polling as a recovery fallback.
- Deprecated
- Security
Upgrade
socket.io-clientto 4.8.4 so projects using the SDK and CLI installws8.21 instead of 8.17.1, which has published advisories (GHSA-96hv-2xvq-fx4p, GHSA-58qx-3vcg-4xpx). The old pin blocked upgradingwswithout a package manager override. - Breaking
Query dashboard APIs reject run tokens and public access tokens without user delegation. Existing API key access, including restricted keys with the required query scopes, is unchanged. MCP dashboard access remains supported through delegated tokens for current organization members.
- Breaking
The legacy
clickhouseevent store is retired: task events now go toclickhouse_v2. If you self-host withEVENT_REPOSITORY_DEFAULT_STORE=clickhouse, switch it toclickhouse_v2and follow the self-hosting guide to copy older events, which no longer show until you do. - New
Deployed tasks now keep a valid short-lived run token for their whole run: the token is refreshed during long runs and before a run resumes from a checkpoint. A warm-started task no longer keeps the previous run's token when the next run has none, and run credentials are left out of runner debug logs.
- Security
- Fixed
Fix
trigger deployfailing on self-hosted instances with custom base images. Stages built on a custom image now keep the trust store that image ships with.
- Fixed
171 other lines we could not sort, mostly version bumps
- 4.8.8
The remote MCP server can now list the tags used on your runs, search and read your logs, add tags, update metadata, reset idempotency keys and reschedule delayed runs, and run details now include the run's metadata values. It can also list, read, create and abort bulk actions that cancel or replay many runs at once, and you approve every bulk action it creates. It can also read what a run streamed. Edits that would change nothing are refused without asking you to approve them.
- 4.8.8
The dashboard now shows only the last four characters of root API keys for all projects. Existing root keys still work, but you can no longer copy them from the dashboard. Create a separate API key for each new integration.
- 4.8.8
The remote MCP server now offers new OAuth scopes for errors, queues, tasks, batches, waitpoints, environments, deployments, branches, environment variable names and project settings. Existing connections keep the access they already have.
- 4.8.8
External OIDC token requests now count against the same environment rate limit as other API requests, with the per-run limit unchanged.
- 4.8.8
A run's Session link now opens the session at that run.
- 4.8.8
Reopening the time filter keeps an exact date range selected instead of switching back to "in the last".
- 4.8.7
Worker registration now refuses task source files that are too large once decompressed or aren't valid text, with an error that names the file.
- 4.8.7
The session page now says when earlier conversation messages couldn't be loaded, with a retry, and closing a session keeps the view you were on.
- 4.8.7
On a live run's trace, "Errors only" and search now pick up a span that fails or gets a new name after it first appeared.
- 4.8.7
Alert webhook URLs that point at private or reserved network addresses are now rejected in more cases.
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.