[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@trigger.dev/build@4.8.2

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.8.2

trigger.dev@4.8.2

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/core@4.8.2
  • @trigger.dev/build@4.8.2
  • @trigger.dev/schema-to-json@4.8.2

@trigger.dev/core@4.8.2

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/linear@4.8.2

Patch Changes

• Updated dependencies:
  • @trigger.dev/sdk@4.8.2
  • @trigger.dev/core@4.8.2

@trigger.dev/python@4.8.2

Patch Changes

• Updated dependencies:
  • @trigger.dev/sdk@4.8.2
  • @trigger.dev/core@4.8.2
  • @trigger.dev/build@4.8.2

@trigger.dev/react-hooks@4.8.2

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.8.2

@trigger.dev/redis-worker@4.8.2

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.8.2

@trigger.dev/rsc@4.8.2

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/core@4.8.2

@trigger.dev/schema-to-json@4.8.2

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.8.2

@trigger.dev/slack@4.8.2

Patch Changes

• Updated dependencies:
  • @trigger.dev/sdk@4.8.2
  • @trigger.dev/core@4.8.2

@trigger.dev/sdk@4.8.2

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).

• Updated dependencies:

  • @trigger.dev/core@4.8.2

[coderabbitai]

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: d9b05583-16c4-47cb-bd7d-fb36b22696b0

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.