Trigger.dev Release Notes

trigger.dev v4.7.3

Upgrade

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.7.3

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-7-3

What's changed

Breaking changes

• Creating or resuming a session with POST /api/v1/sessions now requires both session-write and task-trigger permissions. Scoped keys and public tokens must grant write:sessions (or access to the target session) and permission to trigger its task.

Improvements

• Update the minimatch dependency to ^10.2.3. (5236799b7)
• Add trigger.dev orgs list to show the organizations you belong to, with their slugs and IDs. Use the slug with trigger.dev projects create --org, including for organizations that don't have any projects yet. trigger.dev projects create now activates the Free plan for organizations that don't have a plan yet, matching trigger.dev init. (68ee6be4b) …

Upgrade

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

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-7-2

What's changed

Improvements

• Use the current Node.js LTS for deployments whose runtime is unset or set to "node". Set a versioned runtime such as "node-24" to keep deployments pinned to that Node.js major. (9ecdf735e)
• chat.agent now sends parallel tool results to the model in the order the tools were called, the same order the next turn's history uses. Models that bind their thinking to the exact conversation (Claude Sonnet 5.5, Claude Opus 5.5, Claude Fable 5.1) no longer lose a turn's reasoning, or fail the request on accounts that enforce the check, when its tools finish out of order. (760737258) …

trigger.dev v4.7.1

Upgrade

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.7.1

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-7-1

What's changed

Improvements

• trigger.dev init now stops with a clear error when the target directory has no package.json, instead of installing packages into a parent project. A custom task directory entered during interactive init <path> is now written to trigger.config.ts relative to the project directory. (9499bd2a8)

Server changes

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

• The CLI and MCP authorization page now shows the account and organizations you're granting access to.

All packages: v4.7.1

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

Contributors

Chris Arderne, github-actions[bot]

Full changelog: https://github.com/triggerdotdev/trigger.dev/compare/v4.7.0...v4.7.1

trigger.dev v4.7.0

Upgrade

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.7.0

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-7-0

What's changed

Improvements

• Chat agents can now scope concurrency per session. Pass concurrencyKey (for example, your chat ID or tenant ID) and trigger-time named limits via triggerConfig.concurrency when starting a chat session, from chat.createStartSessionAction, the AgentChat client, or a handover. Keys are never defaulted, so a session without one shares the task's keyless pool. (ea9758117)

  const start = chat.createStartSessionAction("support-chat", {
  triggerConfig: { concurrencyKey: user.id },
  });
  

• Concurrency limits can now be paused and resumed, just like queues: concurrencyLimits.pause(name) stops every run holding the limit from being dequeued while keeping its configured bounds, and concurrencyLimits.resume(name) starts them again. (fa94febb6)

trigger.dev v4.6.4

This release fixes a Zod import bug in 4.6.0 through 4.6.3 that could cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in package.json. Cold starts were unaffected. Affected runs were automatically requeued. No data has been lost.

Upgrade

Redeploy your tasks with the latest CLI:

npx trigger.dev@latest deploy

If you pin the CLI version, update it to 4.6.4 or later before redeploying. Existing deployments need a redeploy to receive the fix.

To update your project packages:

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.6.4

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-6-4

All packages: v4.6.4

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

Contributors

github-actions[bot], Dan Sutton, Chris Arderne

Full changelog: https://github.com/triggerdotdev/trigger.dev/compare/v4.6.3...v4.6.4

trigger.dev v4.6.3

[!WARNING] A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in package.json. Cold starts are unaffected by this bug. No data has been lost.

Redeploy with npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.

Upgrade

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.6.3

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-6-3

What's changed

Improvements

• Show how to override the default cron window in schedule policy warnings. (630eb75d1)

• Thrown error cause chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. (4f36f614b)

trigger.dev v4.6.2

[!WARNING] A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in package.json. Cold starts are unaffected by this bug. No data has been lost.

Redeploy with npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.

Upgrade

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.6.2

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-6-2

What's changed

Improvements

• Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads. (76031b0a1) …

trigger.dev v4.6.1

[!WARNING] A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in package.json. Cold starts are unaffected by this bug. No data has been lost.

Redeploy with npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.

Upgrade

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.6.1

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-6-1

What's changed

Improvements

• Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces. (723fde4a8)
• New CLI commands: projects create/get/rename, runs list/get/replay/cancel, and env set (5bcd1a9fa) …

trigger.dev v4.6.0

[!WARNING] A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in package.json. Cold starts are unaffected by this bug. No data has been lost.

Redeploy with npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.

Upgrade

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.6.0

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-6-0

What's changed

Breaking changes

• Minimum supported Zod version is now 3.25.56 released in June 2025. Trigger.dev now uses Zod 4 by default. Projects using Zod 3.25.56 or later 3.x releases remain supported. (#4039). Zod remains a runtime dependency of packages that execute schemas, so existing and new installations continue to receive it automatically. The matching peer dependency range allows package managers to reuse either a compatible Zod 3 or Zod 4 installation from your project. …

trigger.dev v4.5.16

Upgrade

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 Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.5.16

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-5-16

What's changed

Improvements

• The trigger.dev deploy and trigger.dev dev commands now warn (with the suggested fix) when your code loads a package through createRequire() that won't be available in the deployed image. Previously it would fail at runtime in production to load the package. Deploys also now show bundler warnings for your code instead of discarding them. (#4851)

Bug fixes

• Fixes an issue introduced in 4.5.11 that made deploy image builds of projects with large dependency trees noticeably slower. (#4878)

Server changes

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

• A durable guard improves reliability for runs waiting on triggerAndWait or batchTriggerAndWait if there's a database error that interrupts a child run finishing. (#4849)

All packages: v4.5.16 …