@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.8.6 to 4.8.7
1 release in betweenevery note read
Release by release
- 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
4 other lines we could not sort, mostly version bumps
- 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.