chore: release v4.8.2 by github-actions[bot] · Pull Request #5073 · triggerdotdev/trigger.dev

github-actions · 2026-10-26T10:44:01Z

Summary

9 improvements, 15 bug fixes.

Breaking changes

The legacy clickhouse event store is retired: task events now go to clickhouse_v2. If you self-host with EVENT_REPOSITORY_DEFAULT_STORE=clickhouse, switch it to clickhouse_v2 and follow the self-hosting guide to copy older events, which no longer show until you do.

Improvements

Upgrade socket.io-client to 4.8.4 so projects using the SDK and CLI install ws 8.21 instead of 8.17.1, which has published advisories (GHSA-96hv-2xvq-fx4p, GHSA-58qx-3vcg-4xpx). The old pin blocked upgrading ws without a package manager override. (2df9860b4)
Adds the bun-1.4 runtime. runtime: "bun-1.4" deploys on Bun 1.4.4 in a Bun-only image with no Node.js binary, and the run controller itself runs under Bun. runtime: "bun" is unchanged (Bun 1.3 with Node.js alongside it); bun-legacy is accepted as an explicit spelling of the same runtime. On Bun 1.4 the worker no longer crashes at startup on the --no-warnings=ExperimentalWarning flag. (a8a87850b)
Run metadata operations now reject JSON-path keys that use escaped dots to reach __proto__, constructor or prototype. (dce5048a8)
runs.subscribeToRun now ends after the run completes. The for await loop exits right after the update with the final status, and the subscription stops its connection, so a script that subscribes to a run exits on its own. Pass stopOnCompletion: false to keep the subscription open after completion. (485ab83aa)
The bundled trigger-cost-savings skill now notes that a webhook delivery starts no run when no subscriber's filter matches, so it costs no compute. (#5051)
Stream a sub-agent's reply through a parent tool call with chat.forwardSubAgent. Each chunk is written to the parent chat once and the tool resolves with the sub-agent's final message, so streaming a sub-agent costs bytes in proportion to its reply. Yielding stream.messages() snapshots resends the whole message on every chunk, which grows with the square of the reply. (bdc994c4d)
```
execute: async ({ topic }, { toolCallId, abortSignal }) => {
const stream = await researcher.sendMessage(topic, { abortSignal });
return await chat.forwardSubAgent(stream, { toolCallId });
},
```
Render it while it runs with useSubAgentMessages() from @trigger.dev/sdk/chat/react (or createSubAgentMessages() outside React).

Bug fixes

Fix chat.inject messages added from a tool mid-turn being saved before the assistant's response. They now stay after the tool result, where the model saw them, so the next turn keeps the same prompt prefix. If you roll @trigger.dev/sdk back to an earlier version, chats saved by this version lose these mid-turn chat.inject messages from the model's context, though the chat history shown in the UI keeps them. (fc33769a5)
Fix a chat.agent turn failing after a head start that ended with two or more parallel tool calls. When those tools finished out of call order, the agent sent their results to the model twice on the next step, and the provider rejected the request (Anthropic: "each tool_use must have a single result"). Each handed-over tool result is now sent once. (d06ee5825)

Server changes

These changes affect the self-hosted Docker image and Trigger.dev Cloud:

The run page now loads large traces progressively and updates live runs incrementally, so big traces open faster and open run pages no longer reload the whole trace while a run is executing. The run trace API can also page large traces.
Archiving unused queues from the Concurrency page is now available on all instances, including self-hosted.
Session external ids can no longer contain a /channels path segment (for example chat-1/channels/support) or end in :channels, since both forms name a session's channels. Creating a session with one now returns a 422 validation error.
Fix the batch results API returning "Batch not found" for some batches that the batch retrieve API could see.
Fix the run page continuing to live-update forever for some cancelled runs. These runs now show as finished, and loading their trace is faster.
Fix fetching the trace of a child run through the API sometimes being very slow or failing. These requests now return quickly.
Changing your email address now requires clicking a confirmation button after opening the emailed link.
Fix intermittent read and subscription errors when multiple clients first open the same realtime stream.
Deleting an organization now cancels its billing subscription.
Queries now reject an alias that reuses a table's alias in the same SELECT, unless the aliased expression contains an aggregate or window function (count() AS runs FROM runs still works).
Queries using WITH <expression> AS <name> now run instead of failing with a syntax error, and the name can be used in the rest of the query. The name can't reuse a table alias used anywhere in the query.
Fix a rare case where clock skew between run engine instances could leave a run executing after its task finished, or stop a wait from ever resuming. A run's state changes are now always ordered in the order they happened, regardless of clock skew.
A run whose attempt start was interrupted no longer gets stuck executing without its task ever running, then failing as stalled.
New runs a session starts are now always linked to their session, so their Agent tab no longer fails to load because the link was missing.
Deleting an organization now uninstalls its Vercel integration. A Vercel installation disabled on Vercel's side is reported as such instead of as an expired connection, and removing it no longer reports success.
Promoting or rolling back a deployment now updates your webhook endpoints to match the deployment that's now current.

Raw changeset output

Releases

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:
- @trigger.dev/[email protected]

[email protected]

Patch Changes

Upgrade socket.io-client to 4.8.4 so projects using the SDK and CLI install ws 8.21 instead of 8.17.1, which has published advisories (GHSA-96hv-2xvq-fx4p, GHSA-58qx-3vcg-4xpx). The old pin blocked upgrading ws without a package manager override. (2df9860b4)
Adds the bun-1.4 runtime. runtime: "bun-1.4" deploys on Bun 1.4.4 in a Bun-only image with no Node.js binary, and the run controller itself runs under Bun. runtime: "bun" is unchanged (Bun 1.3 with Node.js alongside it); bun-legacy is accepted as an explicit spelling of the same runtime. On Bun 1.4 the worker no longer crashes at startup on the --no-warnings=ExperimentalWarning flag. (a8a87850b)
Updated dependencies:
- @trigger.dev/[email protected]
- @trigger.dev/[email protected]
- @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Run metadata operations now reject JSON-path keys that use escaped dots to reach __proto__, constructor or prototype. (dce5048a8)
Upgrade socket.io-client to 4.8.4 so projects using the SDK and CLI install ws 8.21 instead of 8.17.1, which has published advisories (GHSA-96hv-2xvq-fx4p, GHSA-58qx-3vcg-4xpx). The old pin blocked upgrading ws without a package manager override. (2df9860b4)
runs.subscribeToRun now ends after the run completes. The for await loop exits right after the update with the final status, and the subscription stops its connection, so a script that subscribes to a run exits on its own. Pass stopOnCompletion: false to keep the subscription open after completion. (485ab83aa)
Adds the bun-1.4 runtime. runtime: "bun-1.4" deploys on Bun 1.4.4 in a Bun-only image with no Node.js binary, and the run controller itself runs under Bun. runtime: "bun" is unchanged (Bun 1.3 with Node.js alongside it); bun-legacy is accepted as an explicit spelling of the same runtime. On Bun 1.4 the worker no longer crashes at startup on the --no-warnings=ExperimentalWarning flag. (a8a87850b)

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:
- @trigger.dev/[email protected]
- @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:
- @trigger.dev/[email protected]
- @trigger.dev/[email protected]
- @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:
- @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:
- @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Adds the bun-1.4 runtime. runtime: "bun-1.4" deploys on Bun 1.4.4 in a Bun-only image with no Node.js binary, and the run controller itself runs under Bun. runtime: "bun" is unchanged (Bun 1.3 with Node.js alongside it); bun-legacy is accepted as an explicit spelling of the same runtime. On Bun 1.4 the worker no longer crashes at startup on the --no-warnings=ExperimentalWarning flag. (a8a87850b)
Updated dependencies:
- @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:
- @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:
- @trigger.dev/[email protected]
- @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Fix chat.inject messages added from a tool mid-turn being saved before the assistant's response. They now stay after the tool result, where the model saw them, so the next turn keeps the same prompt prefix. If you roll @trigger.dev/sdk back to an earlier version, chats saved by this version lose these mid-turn chat.inject messages from the model's context, though the chat history shown in the UI keeps them. (fc33769a5)
The bundled trigger-cost-savings skill now notes that a webhook delivery starts no run when no subscriber's filter matches, so it costs no compute. (#5051)
Stream a sub-agent's reply through a parent tool call with chat.forwardSubAgent. Each chunk is written to the parent chat once and the tool resolves with the sub-agent's final message, so streaming a sub-agent costs bytes in proportion to its reply. Yielding stream.messages() snapshots resends the whole message on every chunk, which grows with the square of the reply. (bdc994c4d)
```
execute: async ({ topic }, { toolCallId, abortSignal }) => {
  const stream = await researcher.sendMessage(topic, { abortSignal });
  return await chat.forwardSubAgent(stream, { toolCallId });
},
```
Render it while it runs with useSubAgentMessages() from @trigger.dev/sdk/chat/react (or createSubAgentMessages() outside React).
Fix a chat.agent turn failing after a head start that ended with two or more parallel tool calls. When those tools finished out of call order, the agent sent their results to the model twice on the next step, and the provider rejected the request (Anthropic: "each tool_use must have a single result"). Each handed-over tool result is now sent once. (d06ee5825)
Updated dependencies:
- @trigger.dev/[email protected]

coderabbitai · 2026-10-26T10:44:10Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Repository UI
Review profile: CHILL
Plan: Advanced
Run ID: 58bce641-0069-44a7-9c37-8f6902b317fa

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

devin-ai-integration