View all changelogs

Trigger.dev v4.7.2

Node.js runtime defaults to LTS, chat.agent tool ordering fix, and a download fix for large payloads.

@ericallam@carderne@Mariefay

3 contributors

3 improvements and 1 server change.

Improvements

  • Node.js deployments with runtime unset or set to "node" now use the current Node.js LTS. Set a versioned runtime like "node-24" to pin deployments to a specific Node.js major.
  • chat.agent now sends parallel tool results to the model in the order the tools were called. Models that bind thinking to the exact conversation history (Claude Sonnet 5.5, Claude Opus 5.5, Claude Fable 5.1) no longer lose reasoning or fail when tools complete out of order.
  • Recovering a long unfinished chat.agent response on a continuation run no longer blocks the worker. Response rebuilding is now linear in length and yields to the event loop, keeping heartbeats firing and preventing runs from being killed mid-replay.

Server changes

These changes are included in the v4.7.2 Docker image and are already live on Trigger.dev Cloud:

  • Fix the "Download payload" and "Download output" buttons for large payloads and outputs, which previously downloaded an error file instead of the actual data.

How to upgrade

Update the trigger.dev/* packages to v4.7.2 using your package manager:


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 users: update your Docker image to ghcr.io/triggerdotdev/trigger.dev:v4.7.2.

Trigger.dev v4.7.1

Ready to start building?

Build and deploy your first task in 3 minutes.

Get started now