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

Release notes

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

What's changed

Breaking changes

Trigger.dev v3 is no longer supported. For self-hosted deployments, 4.5.0 is the last version we officially support for running v3; stay on 4.5.0 or upgrade to v4. v3 triggers, batch triggers, reschedules, and deploys now return a clear upgrade message instead of running. (#4236)

Improvements

You can now mark environment variables synced via the syncEnvVars build extension as secrets. Return { name, value, isSecret: true } from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars. (#4203)

Remove the legacy --mcp and --mcp-port options from the dev command. Run the dedicated trigger mcp command to start the Trigger.dev MCP server. (#4246)

Removed the unused ResourceMonitor export from @trigger.dev/core/v3/serverOnly. It was a server-side logging helper with no remaining consumers. (#4244)

Removed the unused @trigger.dev/core/v3/zodNamespace export and the legacy v3 socket message schemas. These were only used by the now-retired v3 engine and have no v4 consumers. (#4236)

Bug fixes

Fix a chat.agent message-loss race where sending a message right after an action (such as an undo) could drop the follow-up's response from the UI until a refresh. (#4234)

Server changes

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

Added EVENT_REPOSITORY_POSTGRES_WRITES_DISABLED to skip all PostgreSQL task-event writes for deployments that store task events in ClickHouse. Leave it off unless EVENT_REPOSITORY_DEFAULT_STORE is clickhouse_v2, otherwise task events are lost. (#4242)

Promo credits: a /promo signup landing page, redeeming a promo code when a new org selects a plan, and showing remaining credits on the usage page. (#4138)

Speed up retrieving a background worker by version. The endpoint no longer runs a slow lookup that scanned the full task table for large deployments; it now reuses data it already loads, so the response is the same but returns much faster. (#4245)

Clearer login error when an email address is blocked by the WHITELISTED_EMAILS setting: the message now explains the address isn't allowed on this instance instead of the ambiguous "This email is unauthorized". (#4220)

Make the native build server the default in project build settings. It's now opt-out, stored as a new disableNativeBuildServer key. Also clarifies in the UI that build settings apply to GitHub-triggered and native build server deployments. (#3980)

Optionally process high-volume telemetry ingestion in parallel for higher throughput under heavy load by setting OTEL_TRANSFORM_WORKER_POOL_ENABLED=1. Off by default. (#4232)

Add a REALTIME_BACKEND_DEFAULT env var to choose the default realtime backend (electric, native, or shadow) for environments whose org has no per-org override. Defaults to electric, so existing behavior is unchanged. (#4231)

Clarified on the Regions page that a region only affects where your runs execute, not where your data is stored. This shows as a tooltip on the Location column and in the confirmation dialog when you change your default region. (#4226)

Improved the reliability of how run data is read and written. (#4237)

Fixed stale login errors: an error from a previous login attempt (for example a rejected email address) no longer keeps reappearing on the login page and no longer makes later, successful attempts look like they failed. (#4220)

The Errors page now shows better details for each error. Errors that don't carry a message — such as errors thrown without a message, or values thrown that aren't Error objects — get a meaningful title instead of all reading "Unknown error", and are grouped by their name (or value) rather than collapsed into a single group. The error type now shows the actual error name, and stack traces now appear where previously they were missing. (#4225)

Return a clear client error when SSO form submissions use an unsupported content type (#4238)

Query page: extracting fields from a run's output with JSON functions (such as JSONExtractString or JSONExtractInt) no longer fails with an "illegal type: JSON" error. (#4221)

All packages: v4.5.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

Chris Arderne, Eric Allam, @d-cs, Matt Aitken, @isshaddad, github-actions[bot], @nicktrn, Saadi Myftija, Oskar Otwinowski, @D-K-P, claude[bot], Wes Mason, James Ritchie

Full changelog: v4.5.3...v4.5.4

Original source

Summary

2 new features, 11 improvements, 5 bug fixes.

Breaking changes

Trigger.dev v3 is no longer supported. For self-hosted deployments, 4.5.0 is the last version we officially support for running v3; stay on 4.5.0 or upgrade to v4. v3 triggers, batch triggers, reschedules, and deploys now return a clear upgrade message instead of running.

(#4236)

Improvements

You can now mark environment variables synced via the syncEnvVars build extension as secrets. Return { name, value, isSecret: true } from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars.

(#4203)

Remove the legacy --mcp and --mcp-port options from the dev command. Run the dedicated trigger mcp command to start the Trigger.dev MCP server.

(#4246)

Removed the unused ResourceMonitor export from @trigger.dev/core/v3/serverOnly. It was a server-side logging helper with no remaining consumers.

(#4244)

Removed the unused @trigger.dev/core/v3/zodNamespace export and the legacy v3 socket message schemas. These were only used by the now-retired v3 engine and have no v4 consumers.

(#4236)

Bug fixes

Fix a chat.agent message-loss race where sending a message right after an action (such as an undo) could drop the follow-up's response from the UI until a refresh.

(#4234)

Server changes

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

Added EVENT_REPOSITORY_POSTGRES_WRITES_DISABLED to skip all PostgreSQL task-event writes for deployments that store task events in ClickHouse. Leave it off unless EVENT_REPOSITORY_DEFAULT_STORE is clickhouse_v2, otherwise task events are lost.

(#4242)

Promo credits: a /promo signup landing page, redeeming a promo code when a new org selects a plan, and showing remaining credits on the usage page.

(#4138)

Speed up retrieving a background worker by version. The endpoint no longer runs a slow lookup that scanned the full task table for large deployments; it now reuses data it already loads, so the response is the same but returns much faster.

(#4245)

Clearer login error when an email address is blocked by the WHITELISTED_EMAILS setting: the message now explains the address isn't allowed on this instance instead of the ambiguous "This email is unauthorized".

(#4220)

Make the native build server the default in project build settings. It's now opt-out, stored as a new disableNativeBuildServer key. Also clarifies in the UI that build settings apply to GitHub-triggered and native build server deployments.

(#3980)

Optionally process high-volume telemetry ingestion in parallel for higher throughput under heavy load by setting OTEL_TRANSFORM_WORKER_POOL_ENABLED=1. Off by default.

(#4232)

Add a REALTIME_BACKEND_DEFAULT env var to choose the default realtime backend (electric, native, or shadow) for environments whose org has no per-org override. Defaults to electric, so existing behavior is unchanged.

(#4231)

Clarified on the Regions page that a region only affects where your runs execute, not where your data is stored. This shows as a tooltip on the Location column and in the confirmation dialog when you change your default region.

(#4226)

Improved the reliability of how run data is read and written.

(#4237)

Fixed stale login errors: an error from a previous login attempt (for example a rejected email address) no longer keeps reappearing on the login page and no longer makes later, successful attempts look like they failed.

(#4220)

The Errors page now shows better details for each error. Errors that don't carry a message — such as errors thrown without a message, or values thrown that aren't Error objects — get a meaningful title instead of all reading "Unknown error", and are grouped by their name (or value) rather than collapsed into a single group. The error type now shows the actual error name, and stack traces now appear where previously they were missing.

(#4225)

Return a clear client error when SSO form submissions use an unsupported content type

(#4238)

Query page: extracting fields from a run's output with JSON functions (such as JSONExtractString or JSONExtractInt) no longer fails with an "illegal type: JSON" error.

(#4221)

Raw changeset output

Releases

@trigger.dev/[email protected]

Patch Changes

You can now mark environment variables synced via the syncEnvVars build extension as secrets. Return { name, value, isSecret: true } from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars.

(#4203)

Updated dependencies:

• @trigger.dev/[email protected]

[email protected]

Patch Changes

Remove the legacy --mcp and --mcp-port options from the dev command. Run the dedicated trigger mcp command to start the Trigger.dev MCP server.

(#4246)

Updated dependencies:

• @trigger.dev/[email protected]
• @trigger.dev/[email protected]
• @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Removed the unused ResourceMonitor export from @trigger.dev/core/v3/serverOnly. It was a server-side logging helper with no remaining consumers.

(#4244)

Removed the unused @trigger.dev/core/v3/zodNamespace export and the legacy v3 socket message schemas. These were only used by the now-retired v3 engine and have no v4 consumers.

(#4236)

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:

• @trigger.dev/[email protected]
• @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

Updated dependencies:

• @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Fix a chat.agent message-loss race where sending a message right after an action (such as an undo) could drop the follow-up's response from the UI until a refresh.

(#4234)

Updated dependencies:

• @trigger.dev/[email protected]

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Original source

Summary

2 new features, 11 improvements, 5 bug fixes.

Breaking changes

Trigger.dev v3 is no longer supported. For self-hosted deployments, 4.5.0 is the last version we officially support for running v3; stay on 4.5.0 or upgrade to v4. v3 triggers, batch triggers, reschedules, and deploys now return a clear upgrade message instead of running. (#4236)

Improvements

You can now mark environment variables synced via the syncEnvVars build extension as secrets. Return { name, value, isSecret: true } from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars. (#4203)

Remove the legacy --mcp and --mcp-port options from the dev command. Run the dedicated trigger mcp command to start the Trigger.dev MCP server. (#4246)

Removed the unused ResourceMonitor export from @trigger.dev/core/v3/serverOnly. It was a server-side logging helper with no remaining consumers. (#4244)

Removed the unused @trigger.dev/core/v3/zodNamespace export and the legacy v3 socket message schemas. These were only used by the now-retired v3 engine and have no v4 consumers. (#4236)

Bug fixes

Fix a chat.agent message-loss race where sending a message right after an action (such as an undo) could drop the follow-up's response from the UI until a refresh. (#4234)

Server changes

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

Added EVENT_REPOSITORY_POSTGRES_WRITES_DISABLED to skip all PostgreSQL task-event writes for deployments that store task events in ClickHouse. Leave it off unless EVENT_REPOSITORY_DEFAULT_STORE is clickhouse_v2, otherwise task events are lost. (#4242)

Promo credits: a /promo signup landing page, redeeming a promo code when a new org selects a plan, and showing remaining credits on the usage page. (#4138)

Speed up retrieving a background worker by version. The endpoint no longer runs a slow lookup that scanned the full task table for large deployments; it now reuses data it already loads, so the response is the same but returns much faster. (#4245)

Clearer login error when an email address is blocked by the WHITELISTED_EMAILS setting: the message now explains the address isn't allowed on this instance instead of the ambiguous "This email is unauthorized". (#4220)

Make the native build server the default in project build settings. It's now opt-out, stored as a new disableNativeBuildServer key. Also clarifies in the UI that build settings apply to GitHub-triggered and native build server deployments. (#3980)

Optionally process high-volume telemetry ingestion in parallel for higher throughput under heavy load by setting OTEL_TRANSFORM_WORKER_POOL_ENABLED=1. Off by default. (#4232)

Add a REALTIME_BACKEND_DEFAULT env var to choose the default realtime backend (electric, native, or shadow) for environments whose org has no per-org override. Defaults to electric, so existing behavior is unchanged. (#4231)

Clarified on the Regions page that a region only affects where your runs execute, not where your data is stored. This shows as a tooltip on the Location column and in the confirmation dialog when you change your default region. (#4226)

Improved the reliability of how run data is read and written. (#4237)

Fixed stale login errors: an error from a previous login attempt (for example a rejected email address) no longer keeps reappearing on the login page and no longer makes later, successful attempts look like they failed. (#4220)

The Errors page now shows better details for each error. Errors that don't carry a message — such as errors thrown without a message, or values thrown that aren't Error objects — get a meaningful title instead of all reading "Unknown error", and are grouped by their name (or value) rather than collapsed into a single group. The error type now shows the actual error name, and stack traces now appear where previously they were missing. (#4225)

Return a clear client error when SSO form submissions use an unsupported content type (#4238)

Query page: extracting fields from a run's output with JSON functions (such as JSONExtractString or JSONExtractInt) no longer fails with an "illegal type: JSON" error. (#4221)

Raw changeset output

Releases

@trigger.dev/[email protected]

Patch Changes

You can now mark environment variables synced via the syncEnvVars build extension as secrets. Return { name, value, isSecret: true } from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars. (#4203)

Updated dependencies:

• @trigger.dev/[email protected]

[email protected]

Patch Changes

Remove the legacy --mcp and --mcp-port options from the dev command. Run the dedicated trigger mcp command to start the Trigger.dev MCP server. (#4246)

Updated dependencies:

• @trigger.dev/[email protected]
• @trigger.dev/[email protected]
• @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Removed the unused ResourceMonitor export from @trigger.dev/core/v3/serverOnly. It was a server-side logging helper with no remaining consumers. (#4244)

Removed the unused @trigger.dev/core/v3/zodNamespace export and the legacy v3 socket message schemas. These were only used by the now-retired v3 engine and have no v4 consumers. (#4236)

@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

Updated dependencies:

• @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:

• @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Fix a chat.agent message-loss race where sending a message right after an action (such as an undo) could drop the follow-up's response from the UI until a refresh. (#4234)

Updated dependencies:

• @trigger.dev/[email protected]

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Original source

What changed

Updates the ClickHouse chat agent example page to match the upgraded example (triggerdotdev/examples#124), which is now a fullstack generative-UI chat app rather than an agent-only project.

Overview / tech stack / features rewritten: Next.js chat app (useChat + useTriggerChatTransport, no API route), a renderVisualization tool taking json-render specs rendered with @json-render/shadcn + shadcn charts (Recharts) + mapcn point maps, and a shared catalog that generates both the system-prompt component reference and tool-call validation.

The agent section now shows the versioned AI Prompt pattern (prompts.define() chat.prompt.set() + chat.toStreamTextOptions({ registry })), with a warning that experimental_telemetry comes from the stored prompt — the docs previously showed a static system: string, which silently ships no LLM observability.

New sections for the shared catalog, the renderVisualization tool, the Next.js chat UI and registry.

Relevant code links updated to the new src/ layout.

Learn more cards now include Frontend and AI Prompts.

Note: merge after triggerdotdev/examples#124 lands, so the GitHub file links resolve.

🤖 Generated with Claude Code

Original source

1 breaking change, 4 improvements, 1 bug fix, and 13 server changes.

Highlights

v3 support removed

Trigger.dev v3 is no longer supported in v4.5.4+. For self-hosted deployments, 4.5.0 is the last version with v3 support. v3 triggers, batch triggers, reschedules, and deploys now return a clear upgrade message instead of executing silently. (#4236)

Secret env vars via syncEnvVars

The syncEnvVars build extension now lets you mark synced variables as secrets. Return isSecret: true alongside any variable and it's stored redacted in the dashboard, the same as manually created secret env vars.

syncEnvVars (async () => {
  return [
    {
      name: "MY_API_KEY",
      value: await fetchSecret(),
      isSecret: true,
    },
    {
      name: "PUBLIC_URL",
      value: "https://example.com",
    },
  ];
});

(#4203)

Improvements

• Removed the --mcp and --mcp-port flags from the dev command. Run trigger mcp to start the MCP server instead. (#4246)
• Removed the unused ResourceMonitor export from @trigger.dev/core/v3/serverOnly. (#4244)
• Removed the unused @trigger.dev/core/v3/zodNamespace export and legacy v3 socket message schemas, which had no v4 consumers. (#4236)

Bug fixes

• Fix a chat.agent message-loss race where sending a message immediately after an action (such as an undo) could drop the response from the UI until a refresh. (#4234)

Server changes

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

• Added EVENT_REPOSITORY_POSTGRES_WRITES_DISABLED to skip all PostgreSQL task-event writes for deployments using ClickHouse as the event store. Only enable if EVENT_REPOSITORY_DEFAULT_STORE is clickhouse_v2, otherwise task events are lost. (#4242)
• Added a promo code system: a /promo signup landing page, promo code redemption when a new org selects a plan, and remaining credits shown on the usage page. (#4138)
• Background worker lookups by version are faster. The endpoint now reuses data it already loads instead of scanning the full task table. (#4245)
• Clearer login error when an email is blocked by WHITELISTED_EMAILS: the message now says the address isn't permitted on this instance instead of "This email is unauthorized". (#4220)
• The native build server is now opt-out by default. Project build settings store this as disableNativeBuildServer. The UI also clarifies that build settings apply to GitHub-triggered and native build server deployments. (#3980)
• Added OTEL_TRANSFORM_WORKER_POOL_ENABLED=1 to process high-volume telemetry ingestion in parallel for higher throughput under heavy load. Off by default. (#4232)
• Added REALTIME_BACKEND_DEFAULT env var to set the default realtime backend (electric, native, or shadow) for environments without a per-org override. Defaults to electric, so existing behavior is unchanged. (#4231)
• Clarified on the Regions page that a region only affects where runs execute, not where data is stored. Shown as a tooltip on the Location column and in the region-change confirmation dialog. (#4226)
• Improved reliability of run data reads and writes. (#4237)
• Fixed stale login errors: a rejected email from a prior attempt no longer persists on the login page or makes later successful attempts appear to have failed. (#4220)
• Errors page now shows better detail for errors without a message. Errors thrown without a message, or non-Error values, get a meaningful title instead of "Unknown error", are grouped by name or value, and include stack traces where previously they were missing. (#4225)
• Return a clear client error when SSO form submissions use an unsupported content type. (#4238)
• Query page: JSONExtractString, JSONExtractInt, and similar JSON functions no longer fail with "illegal type: JSON". (#4221)

How to upgrade

Update the trigger.dev/* packages to v4.5.4 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.5.4.

Original source

Run your tasks in AWS US West (Oregon). A third worker region alongside US East and Europe, for lower latency on the West Coast and more US redundancy.

US West (Oregon) is live on the Regions page. Head to your dashboard and select us-west-2 to make it your default worker region.

Three regions to choose from

Trigger.dev now runs managed workers in three regions:

• us-east-1 (US East, Virginia)
• us-west-2 (US West, Oregon)
• eu-central-1 (Europe, Frankfurt)

Static IPs are available per region, so you can connect to databases and APIs behind an IP allowlist from whichever region runs your tasks.

Try it

Set your default region on the Regions page in your dashboard, and suggest the regions you'd like us to add next.

Original source

Sync secrets from Infisical straight into your Trigger.dev environment variables. Keep Infisical as your source of truth, with no build step or CLI required.

Infisical is an open source secrets manager. If your API keys and credentials already live there, you can now connect it to Trigger.dev and have those secrets land in your environment variables.

Until now, the way to pull Infisical secrets into Trigger.dev was the syncEnvVars build extension, which resolves them at build time when you deploy. The new native Secret Sync lives inside Infisical and pushes secrets straight onto your Trigger.dev environment variables page. You set it up once, then manage everything from Infisical.

How it works

Two pieces, both set up from the Infisical dashboard:

1. Connect your account. Add a Trigger.dev App Connection in Infisical using a Personal Access Token. Self-hosting? Point it at your own instance URL. Trigger.dev Cloud is the default.
2. Create a Secret Sync. Pick the connection, choose an organization and project (pulled live from your Trigger.dev account), select the target environment (Production, Staging, Development, or Preview), and point it at the secret path you want to sync.

Once it's running, update a secret in Infisical and the sync pushes it to Trigger.dev. Your tasks pick up the new value on their next run, no redeploy. It overwrites only the keys it syncs, so the variables you set by hand can be left alone.

Marked as secret by default

The sync has a Mark variables as secret option, on by default. Synced values are stored as secret environment variables in Trigger.dev, so they're redacted when read back on the environment variables page, the same as any secret you set by hand.

Getting started

You'll need a Trigger.dev Personal Access Token (dashboard, account menu, Personal Access Tokens) and an Infisical project. Then follow the Trigger.dev Secret Sync guide to wire it up.

Original source

Fixed TypeScript declaration emit for chat.agent exports, plus two server fixes.

1 bug fix and 2 server changes.

Bug fixes

• Fix TS2742 ("inferred type cannot be named") when exporting a chat.agent from a project with declaration emit. ChatTaskWirePayload and ChatInputChunk are now declared in the public @trigger.dev/sdk/chat subpath, so inferred agent types emit portable declarations and the wire types are directly importable. (#4218)

Server changes

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

• Reduce primary database load on the runs page by serving its empty-state check from ClickHouse instead of Postgres. (#4202)
• Fixed submitting your email on the login page reloading back to an empty form instead of showing the magic link confirmation screen. (#4215)

How to upgrade

Update the trigger.dev/* packages to v4.5.3 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.5.3.

Original source

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

Release notes

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

What's changed

Breaking changes

Removed support for the end-of-life v3 trigger dev CLI. Starting a dev session with an old v3 CLI now returns an upgrade message instead of connecting - upgrade to the v4 CLI to continue using trigger dev. (#4198)

Bug fixes

Fix TS2742 ("inferred type cannot be named") when exporting a chat.agent from a project with declaration emit: ChatTaskWirePayload and ChatInputChunk are now declared in the public @trigger.dev/sdk/chat subpath, so inferred agent types emit portable declarations and the wire types are directly importable. (#4218)

Server changes

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

Reduce primary database load on the runs page by serving its empty-state check from ClickHouse instead of Postgres. (#4202)

Fixed submitting your email on the login page reloading back to an empty form instead of showing the magic link confirmation screen. (#4215)

All packages: v4.5.3

@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

Eric Allam, Oskar Otwinowski, github-actions[bot], Matt Aitken, James Ritchie, claude[bot], Chris Arderne, @nicktrn

Full changelog: v4.5.2...v4.5.3

Original source

Summary

1 improvement, 2 bug fixes.

Breaking changes

Removed support for the end-of-life v3 trigger dev CLI. Starting a dev session with an old v3 CLI now returns an upgrade message instead of connecting - upgrade to the v4 CLI to continue using trigger dev.
(#4198)

Bug fixes

Fix TS2742 ("inferred type cannot be named") when exporting a chat.agent from a project with declaration emit: ChatTaskWirePayload and ChatInputChunk are now declared in the public @trigger.dev/sdk/chat subpath, so inferred agent types emit portable declarations and the wire types are directly importable.
(#4218)

Server changes

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

Reduce primary database load on the runs page by serving its empty-state check from ClickHouse instead of Postgres.
(#4202)

Fixed submitting your email on the login page reloading back to an empty form instead of showing the magic link confirmation screen.
(#4215)

Raw changeset output

Releases

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:

• @trigger.dev/[email protected]

[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]
• @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

Updated dependencies:

• @trigger.dev/[email protected]
• @trigger.dev/[email protected]

Patch Changes

Updated dependencies:

• @trigger.dev/[email protected]
• @trigger.dev/[email protected]

Patch Changes

Fix TS2742 ("inferred type cannot be named") when exporting a chat.agent from a project with declaration emit: ChatTaskWirePayload and ChatInputChunk are now declared in the public @trigger.dev/sdk/chat subpath, so inferred agent types emit portable declarations and the wire types are directly importable.
(#4218)

Updated dependencies:

• @trigger.dev/[email protected]
• @trigger.dev/[email protected]

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Original source

Summary

1 improvement, 2 bug fixes.

Breaking changes

Removed support for the end-of-life v3 trigger dev CLI. Starting a dev session with an old v3 CLI now returns an upgrade message instead of connecting - upgrade to the v4 CLI to continue using trigger dev.

(#4198)

Bug fixes

Fix TS2742 ("inferred type cannot be named") when exporting a chat.agent from a project with declaration emit: ChatTaskWirePayload and ChatInputChunk are now declared in the public @trigger.dev/sdk/chat subpath, so inferred agent types emit portable declarations and the wire types are directly importable.

(#4218)

Server changes

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

Reduce primary database load on the runs page by serving its empty-state check from ClickHouse instead of Postgres.

(#4202)

Fixed submitting your email on the login page reloading back to an empty form instead of showing the magic link confirmation screen.

(#4215)

Raw changeset output

Releases

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:

@trigger.dev/[email protected]

[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]

@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

Updated dependencies:

@trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Updated dependencies:

@trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

Fix TS2742 ("inferred type cannot be named") when exporting a chat.agent from a project with declaration emit: ChatTaskWirePayload and ChatInputChunk are now declared in the public @trigger.dev/sdk/chat subpath, so inferred agent types emit portable declarations and the wire types are directly importable.

(#4218)

Updated dependencies:

@trigger.dev/[email protected]

@trigger.dev/[email protected]

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Original source

2 new features, 8 improvements, 10 bug fixes and 7 security patches.

Highlights

API and SDK support for bulk actions

Bulk actions allow runs to be re-run based on a filter or run IDs. Now it's also available via API and in the official SDK. Create, list, retrieve, poll and abort bulk actions. Runs can be targeted to a different compute region, just like in the web UI. (#4105)

const action = await runs.bulk.replay({
  filter: {
    status: "FAILED",
    taskIdentifier: "sync-customer",
    period: "24h",
  },
  name: "Replay failed customer syncs",
  targetRegion: "eu-central-1",
});

Lifecycle event callbacks for TriggerChatTransport

TriggerChatTransport and useTriggerChatTransport now accept an onEvent callback that fires on typed lifecycle events: message sent, stream connected, first chunk received, and turn complete. Use it to track send latency, time-to-first-token, and detect stalled turns with just a few lines of client code. (#4187)

const transport = new TriggerChatTransport({
  // ...
  onEvent: (event) => {
    if (event.type === "message-sent") metrics.timing("chat.send_ms", event.durationMs);
    if (event.type === "first-chunk") metrics.timing("chat.ttft_ms", event.sinceSendMs ?? 0);
  },
});

AI Chat frontend docs

Improvements

• Large batch payloads now offload to object storage instead of riding inline in the trigger request. batchTrigger and batchTriggerAndWait (and the by-id and by-task variants) offload any per-item payload over 128KB before sending, the same way single trigger and triggerAndWait already do, so a big batch no longer blows past the API body limit. (#4165)
• Removed internal helpers that were only used by the end-of-life v3 self-hosted compute providers. (#4194)
• The environment and branch selector dropdown will automatically revalidate when opened so that new branches show up. (#4171)
• A cleaner sign-in flow: request a magic link right from the login page, or continue with SSO. (#4182)
• Serve PostHog analytics from a same-origin /ph path that reverse-proxies to PostHog Cloud EU, following PostHog's first-party reverse-proxy guidance. (#4183)
• Refreshed the SSO & Directory Sync settings page layout and copy. (#4196)
• Migrated the webapp to Tailwind CSS v4 with a CSS-first @theme. Semantic color tokens are now CSS variables overridable per theme. Tailwind runs through @tailwindcss/postcss; plugins replaced or upgraded to v4-compatible versions. (#4139)
• Replaced raw charcoal-* Tailwind classes with semantic theme tokens across the dashboard. Adds surface, border and text tokens to the themable layer so future themes only override CSS variables. (#4139)

Bug fixes

• Fix chat turns that throw, for example from an onTurnStart hook, leaking their message listener, which lost or duplicated messages sent during later turns. (#4176)
• Fix chat.agent and chat.createSession permanently dropping user messages when several arrived during a single turn: every buffered message is now dispatched as its own turn instead of only the first. (#4176)
• Fix chat continuation runs replaying already-answered messages: turns delivered while the run was suspended now advance the session.in resume cursor, so a new run picks up exactly where the previous one left off. (#4176)
• Fix chat.createSession swallowing a message sent shortly after stopping a turn: the turn's message listener now detaches when the stream settles, so those messages run as the next turn. (#4176)
• Anchor batch item run-ops residency on the batch's own friendlyId so a mid-batch flag change can no longer mint an item into a different physical store than its BatchTaskRun row. (#4178)
• AI generation cost now uses the exact provider-reported cost from OpenRouter/Vercel AI Gateway when present, instead of catalog pricing, so cache-discounted and fallback-routed requests match the amount the provider actually billed. (#4186)
• Deleting a project no longer triggers a slow database cleanup that could hang on projects with many runs. (#4191)
• Fixed the agent playground chat failing to send messages, with "Failed to fetch" errors in some environments. Messages now reach the agent reliably. (#4193)
• Deploying with an outdated CLI could produce an image that fails to start on every run. These deploys are now stopped before going live, with a message asking you to upgrade the CLI and re-deploy. (#4184)
• Runs resuming after a wait no longer fail with TASK_EXECUTION_ABORTED when the database is briefly unreachable; the resume endpoint returns a retryable response for transient infrastructure errors instead of a permanent one. (#4161)

Security

• Harden account and access-control handling across auth, RBAC, org membership, and impersonation. (#4199)
• Harden URL handling for alert webhooks and platform notifications. (#4199)
• Harden the query and prompt-override APIs and rate-limit the query ai-title endpoint. (#4199)
• Improve redaction of secrets from debug logs. (#4199)
• Tighten environment scoping when replaying a run. (#4199)
• Scope run, batch, and trigger lookups to the caller's tenant. (#4199)
• Honor the MCP server's --dev-only flag. (#4199)

How to upgrade

Update the trigger.dev/* packages to v4.5.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.5.2.

Original source

trigger.dev v4.5.2

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

Release notes

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

What's changed

Security

Harden account and access-control handling across auth, RBAC, org membership, and impersonation. (#4199)

Harden URL handling for alert webhooks and platform notifications. (#4199)

Harden the query and prompt-override APIs and rate-limit the query ai-title endpoint. (#4199)

Improve redaction of secrets from debug logs. (#4199)

Tighten environment scoping when replaying a run. (#4199)

Scope run, batch, and trigger lookups to the caller's tenant. (#4199)

Honor the MCP server's --dev-only flag. (#4199)

Features

Bulk actions allow runs to be re-run based on a filter or run IDs. Now it's also available via API and in the official SDK. Create, list, retrieve, poll and abort bulk actions. Runs can be targeted to a different compute region, just like in the web UI. (#4105)

Improvements

Large batch payloads now offload to object storage instead of riding inline in the trigger request. batchTrigger and batchTriggerAndWait (and the by-id and by-task variants) offload any per-item payload over 128KB before sending, the same way single trigger and triggerAndWait already do, so a big batch no longer blows past the API body limit. (#4165)

Removed internal helpers that were only used by the end-of-life v3 self-hosted compute providers. (#4194)

Add an onEvent callback to TriggerChatTransport / useTriggerChatTransport that emits typed lifecycle events for sends, stream connects, first chunk, and turn completion. Send-success metrics, time-to-first-token, and "sent but never answered" watchdogs become a few lines of client code. (#4187)

onEvent: (event) => {
if (event.type === "message-sent") metrics.timing("chat.send_ms", event.durationMs);
if (event.type === "first-chunk") metrics.timing("chat.ttft_ms", event.sinceSendMs ?? 0);
},

The environment and branch selector dropdown will automatically revalidate when opened so that new branches show up. (#4171)

A cleaner sign-in flow: request a magic link right from the login page, or continue with SSO. (#4182)

Serve PostHog analytics from a same-origin /ph path that reverse-proxies to PostHog Cloud EU, following PostHog's first-party reverse-proxy guidance. (#4183)

Refreshed the SSO & Directory Sync settings page layout and copy. (#4196)

Migrated the webapp to Tailwind CSS v4 with a CSS-first @theme. Semantic color tokens are now CSS variables overridable per theme. Tailwind runs through @tailwindcss/postcss; plugins replaced or upgraded to v4-compatible versions. (#4139)

Replaced raw charcoal-* Tailwind classes with semantic theme tokens across the dashboard. Adds surface, border, and text tokens to the themable layer so future themes only override CSS variables. (#4139)

Bug fixes

Fix chat turns that throw, for example from an onTurnStart hook, leaking their message listener, which lost or duplicated messages sent during later turns. (#4176)

Fix chat.agent and chat.createSession permanently dropping user messages when several arrived during a single turn: every buffered message is now dispatched as its own turn instead of only the first. (#4176)

Fix chat continuation runs replaying already-answered messages: turns delivered while the run was suspended now advance the session.in resume cursor, so a new run picks up exactly where the previous one left off. (#4176)

Fix chat.createSession swallowing a message sent shortly after stopping a turn: the turn's message listener now detaches when the stream settles, so those messages run as the next turn. (#4176)

Anchor batch item run-ops residency on the batch's own friendlyId so a mid-batch flag change can no longer mint an item into a different physical store than its BatchTaskRun row. (#4178)

AI generation cost now uses the exact provider-reported cost from OpenRouter/Vercel AI Gateway when present, instead of catalog pricing, so cache-discounted and fallback-routed requests match the amount the provider actually billed. (#4186)

Deleting a project no longer triggers a slow database cleanup that could hang on projects with many runs. (#4191)

Fixed the agent playground chat failing to send messages, with "Failed to fetch" errors in some environments. Messages now reach the agent reliably. (#4193)

Deploying with an outdated CLI could produce an image that fails to start on every run. These deploys are now stopped before going live, with a message asking you to upgrade the CLI and re-deploy. (#4184)

Runs resuming after a wait no longer fail with TASK_EXECUTION_ABORTED when the database is briefly unreachable; the resume endpoint returns a retryable response for transient infrastructure errors instead of a permanent one. (#4161)

All packages: v4.5.2

@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

Contributors

Chris Arderne, Matt Aitken, Eric Allam, James Ritchie, @nicktrn, @d-cs, Katia Bulatova, Wes Mason, github-actions[bot], @isshaddad, @D-K-P, claude[bot]

Full changelog: v4.5.1...v4.5.2

Original source

Summary

UI/layout/copy pass over the org SSO & Directory Sync settings page

(formerly "Identity & Access"). No logic, gates, flags, or data flow changed — server-side auth (manage:sso), Enterprise entitlement, action validation, and data loading are all untouched.

Renamed the nav item, page title, and meta from "Identity & Access" to "SSO & Directory Sync".

Added a reusable SettingsLayout component system (container, section, header, row, block, actions) modeled on /account/security, and refactored the SSO page onto it (section titles, dividers, left title/subtitle + right action rows).

Tightened all UI copy: concise, active voice, consistent labels, no em-dashes.

Select primitive: additive wrap, popoverClassName, and placement props (all default to prior behavior) so role options show a bright title with a wrapping description, right-aligned popover, and no horizontal overflow.

Removed the external-link arrow icon from buttons that open a modal; kept it only on genuinely external actions (Contact us, Open in new tab).

Polished the admin portal link dialog: smaller description, tighter spacing, ClipboardField with a permanent copy button, removed the redundant Copy link button, and a provider-aware Open label (e.g. "Open in WorkOS") derived from the link host with a safe fallback.

SSO page UI

Login with SSO and normal email test (local)

CleanShot.2026-07-09.at.11.30.00.mp4

Test plan

Non-Enterprise org: SSO page shows the upsell state

Enterprise org, non-Owner without manage:sso: 403

Enterprise Owner: verify domains, configure SSO, connect directory, JIT/default/group role selects, and enforcement toggle all work

Role select popovers: bright title + wrapping description, right-aligned, no horizontal scroll

Admin portal dialog: copy button works, "Open in WorkOS" opens the portal in a new tab

Co-authored-by: Cursor [email protected]

Original source