Skip to content

trigger.dev v4.5.0-rc.5

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 Jun 13:14
· 62 commits to main since this release
a730faa

Upgrade

npx trigger.dev@4.5.0-rc.5 update
pnpm dlx trigger.dev@4.5.0-rc.5 update
yarn dlx trigger.dev@4.5.0-rc.5 update 
bunx trigger.dev@4.5.0-rc.5 update

Self-hosted Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.5.0-rc.5

Highlights

  • Adds AI SDK 7 support. The ai peer range now includes v7, and the chat.agent / chat surfaces work against v7's ESM-only build. On v7, install @ai-sdk/otel alongside ai and the SDK registers it for you so experimental_telemetry spans keep flowing into your run traces (v7 stopped emitting them from ai core). v5 and v6 keep working unchanged. (#3833)
  • useTriggerChatTransport now recovers when restored session state points at a session that no longer exists in the current environment (#3816)

Improvements

  • The MCP server no longer tells the AI agent to wait for a run to complete after every trigger_task call. Waiting is now opt-in: the agent only waits when you ask it to (for example "trigger and then wait for it to finish"). This avoids burning tokens polling runs you didn't need to block on and keeps responses clearer. (#3838)
  • Update the bundled OpenTelemetry packages to their latest releases (@opentelemetry/sdk-node 0.218.0, @opentelemetry/core 2.7.1, @opentelemetry/host-metrics 0.38.3). (#3810)
  • envvars.upload now accepts an optional isSecret flag, letting you create the imported variables as secret (redacted) environment variables. When omitted, variables default to non-secret. (#3809)
  • Offload large trigger payloads to object storage before sending the trigger API request. The SDK uploads packets at or above the existing 128KB limit and sends an application/store pointer instead of embedding large JSON in the request body. TriggerTaskRequestBody now validates that application/store payloads are non-empty storage paths. (#3785)

Bug fixes

  • Fix @trigger.dev/core build: cast the underlying log record exporter when calling forceFlush so it typechecks against the updated OpenTelemetry LogRecordExporter type (which no longer declares forceFlush). (#3829)

All packages: v4.5.0-rc.5

@trigger.dev/build, @trigger.dev/core, @trigger.dev/plugins, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev

Full changelog: v4.4.0.5...v4.5.0-rc.5