Helm Chart 4.7.3
Installation
helm upgrade --install trigger \
oci://ghcr.io/triggerdotdev/charts/trigger \
--version "4.7.3"
Changes
See commit history for detailed changes in this release.
An open-source background jobs platform with no timeouts and durable runs.
Release activity
| Jul | Aug | Sep | Oct | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sunday | No releases on Jul 12, 2026 | No releases on Jul 19, 2026 | No releases on Jul 26, 2026 | No releases on Aug 2, 2026 | No releases on Aug 9, 2026 | No releases on Aug 16, 2026 | No releases on Aug 23, 2026 | No releases on Aug 30, 2026 | No releases on Sep 6, 2026 | No releases on Sep 13, 2026 | No releases on Sep 20, 2026 | No releases on Sep 27, 2026 | No releases on Oct 4, 2026 | No releases on Oct 11, 2026 | ||
| Monday | 1 release on Jul 6, 2026 | No releases on Jul 13, 2026 | 1 release on Jul 20, 2026 | 1 release on Jul 27, 2026 | No releases on Aug 3, 2026 | No releases on Aug 10, 2026 | No releases on Aug 17, 2026 | No releases on Aug 24, 2026 | 1 release on Aug 31, 2026 | No releases on Sep 7, 2026 | 1 release on Sep 14, 2026 | No releases on Sep 21, 2026 | No releases on Sep 28, 2026 | No releases on Oct 5, 2026 | No releases on Oct 12, 2026 | |
| Tuesday | No releases on Jul 7, 2026 | 1 release on Jul 14, 2026 | 1 release on Jul 21, 2026 | No releases on Jul 28, 2026 | No releases on Aug 4, 2026 | No releases on Aug 11, 2026 | No releases on Aug 18, 2026 | No releases on Aug 25, 2026 | 3 releases on Sep 1, 2026 | No releases on Sep 8, 2026 | 1 release on Sep 15, 2026 | 1 release on Sep 22, 2026 | No releases on Sep 29, 2026 | 2 releases on Oct 6, 2026 | No releases on Oct 13, 2026 | |
| Wednesday | No releases on Jul 8, 2026 | No releases on Jul 15, 2026 | No releases on Jul 22, 2026 | No releases on Jul 29, 2026 | No releases on Aug 5, 2026 | No releases on Aug 12, 2026 | No releases on Aug 19, 2026 | No releases on Aug 26, 2026 | 1 release on Sep 2, 2026 | No releases on Sep 9, 2026 | 5 releases on Sep 16, 2026 | No releases on Sep 23, 2026 | No releases on Sep 30, 2026 | No releases on Oct 7, 2026 | No releases on Oct 14, 2026 | |
| Thursday | 1 release on Jul 9, 2026 | No releases on Jul 16, 2026 | 1 release on Jul 23, 2026 | 1 release on Jul 30, 2026 | No releases on Aug 6, 2026 | 1 release on Aug 13, 2026 | 6 releases on Aug 20, 2026 | No releases on Aug 27, 2026 | No releases on Sep 3, 2026 | No releases on Sep 10, 2026 | 2 releases on Sep 17, 2026 | No releases on Sep 24, 2026 | 2 releases on Oct 1, 2026 | No releases on Oct 8, 2026 | ||
| Friday | 1 release on Jul 10, 2026 | No releases on Jul 17, 2026 | No releases on Jul 24, 2026 | No releases on Jul 31, 2026 | 1 release on Aug 7, 2026 | No releases on Aug 14, 2026 | No releases on Aug 21, 2026 | 2 releases on Aug 28, 2026 | No releases on Sep 4, 2026 | No releases on Sep 11, 2026 | No releases on Sep 18, 2026 | No releases on Sep 25, 2026 | 4 releases on Oct 2, 2026 | No releases on Oct 9, 2026 | ||
| Saturday | No releases on Jul 11, 2026 | No releases on Jul 18, 2026 | No releases on Jul 25, 2026 | No releases on Aug 1, 2026 | No releases on Aug 8, 2026 | No releases on Aug 15, 2026 | No releases on Aug 22, 2026 | No releases on Aug 29, 2026 | No releases on Sep 5, 2026 | No releases on Sep 12, 2026 | No releases on Sep 19, 2026 | No releases on Sep 26, 2026 | No releases on Oct 3, 2026 | No releases on Oct 10, 2026 |
42 releases since Jul 6, 2026, busiest day 6
Changelog
trigger.dev v4.7.3
Added 4
- Add trigger.dev orgs list command to show organizations you belong to with their slugs and IDs
- trigger.dev projects create command now activates the Free plan for organizations that don't have a plan yet
- chat.createStartSessionAction, chat.headStart and chat.startHeadStart now accept tags for the Session itself to filter chat sessions by tag on the Sessions page
- Self-hosted instances can block sign-in and sign-up from specific email domains with the new BLOCKED_EMAIL_DOMAINS setting
Changed 5
- Creating or resuming a session with POST /api/v1/sessions now requires both session-write and task-trigger permissions, with scoped keys and public tokens needing write:sessions access
- Update the minimatch dependency to ^10.2.3
- Run traces now appear almost immediately and load progressively, with much larger traces viewable than before
- The Logs page loads and searches faster, and busy environments no longer fail to load it
- Logs page searches that are too expensive now show a message suggesting a narrower range instead of a generic error
Fixed 5
- Reports filed with the submit_feedback MCP tool now reach the Trigger.dev team
- Stopping a chat.agent turn whose run() returns a streamText result no longer sends an error chunk
- Fix a rare case where a run could stay stuck executing after the child run or wait it was waiting on had completed
- Deployments with an unsupported runtime now fail with a 400 that names the supported runtimes instead of a generic 500
- Preserve the cancellation reason when a run that was executing is finalized instead of replacing it with the default text
Helm Chart 4.7.2
See commit history for detailed changes in this release.
trigger.dev v4.7.2
Changed 1
- Use the current Node.js LTS for deployments whose runtime is unset or set to "node", and allow versioned runtimes such as "node-24" to keep deployments pinned to that Node.js major
Fixed 3
- chat.agent now sends parallel tool results to the model in the order the tools were called, fixing issues where models binding their thinking to the exact conversation lose reasoning or fail requests when tools finish out of order
- Recovering a long unfinished chat.agent response on a continuation run no longer blocks the worker by rebuilding the response from streamed chunks in linear time and yielding to the event loop
- Fix the "Download payload" and "Download output" buttons for large payloads and outputs, which were downloading an error file instead of the data
Helm Chart 4.7.1
See commit history for detailed changes in this release.
trigger.dev v4.7.1
Changed 3
- 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
- Custom task directory entered during interactive init <path> is now written to trigger.config.ts relative to the project directory
- The CLI and MCP authorization page now shows the account and organizations you are granting access to
Helm Chart 4.7.0
See commit history for detailed changes in this release.
trigger.dev v4.7.0
Added 8
- Chat agents can now scope concurrency per session using concurrencyKey parameter in triggerConfig.concurrency
- Concurrency limits can now be paused and resumed using concurrencyLimits.pause() and concurrencyLimits.resume()
- New concurrency option for tasks to control concurrency with inline shapes and named concurrency limits
- New concurrencyLimits namespace with list(), retrieve(), override(), and reset() methods to manage limits at runtime
- Chat streams now report stalled status after five retries of a connected stream that sends no records
- Webhook verifier artifacts can now declare provider response contract including respondStatus and GET verification flow
- HMAC verifiers can read timestamp from a body field for replay window validation
- Optional onSettled callback added to TriggerChatTransport.sendAction() for input processing confirmation
Changed 3
- Chat agents now return to a durable wait when a session wake does not deliver a matching message
- Queue reads now report a version field that discriminates between V1 and V2 queue shapes
- Steering messages now remain in context across agent steps and keep their original position in saved conversations
Deprecated 2
- Queue-level concurrencyLimit option is deprecated in favor of the task concurrency option
- queues.overrideConcurrencyLimit and queues.resetConcurrencyLimit are deprecated in favor of concurrencyLimits.override and concurrencyLimits.reset
trigger.dev v4.6.4
Fixed 1
- Fix Zod import bug in versions 4.6.0 through 4.6.3 that caused warm starts to fail and delayed runs by approximately five minutes when using npm with Zod 3 pinned in package.json
Helm Chart 4.6.3
See commit history for detailed changes in this release.
trigger.dev v4.6.3
Changed 4
- Show how to override the default cron window in schedule policy warnings
- Thrown error cause chains are now captured and shown in the dashboard, CLI dev output, and failure alerts, flattened outermost first and capped at five causes
- Error cause chains ride on the error of API and realtime run records as a causes array, and triggerAndWait and triggerAndSubscribe rebuild it as a native cause on the error they hand back
- Keep summarized assistant steps and tool results out of future chat.agent() model context after inner compaction while preserving the full visible conversation
Helm Chart 4.6.2
See commit history for detailed changes in this release.
Helm Chart 4.5.16
See commit history for detailed changes in this release.
Helm Chart 4.6.1
See commit history for detailed changes in this release.
Helm Chart 4.6.0
See commit history for detailed changes in this release.
trigger.dev v4.6.2
Changed 6
- Show warm idle time and durable waits separately in chat agent traces, with durable waits opening the waitpoint inspector while waiting and after completion
- Shorten message span names and remove repeated session IDs from message-wait and default output-stream spans
- Update chat.agent between-turns compaction check to receive the last step's token usage instead of the turn's sum over every tool-calling step
- Replace spliced partial with full reconversion directly in the model lane for head-start handovers whose pending tool call completes under the same message id
- Make turnUsage available as a separate figure on the event for chat.agent between-turns compaction
- Update billing limit banner to let you choose to run without a limit instead of requiring settings access to dismiss it
Fixed 1
- Match org member invite emails case-insensitively so invites with different email casing can be accepted
Security 6
- Authorize stored realtime payload and output downloads against their owning run, limiting access for public tokens while maintaining large packet hydration for run-, task-, tag-, and batch-scoped tokens
- Validate resource IDs when creating scoped public tokens and reject explicitly empty IDs instead of interpreting them as type-wide permissions
- Limit public access tokens created through the JWT endpoint to the API key's permissions and a maximum 24-hour lifetime
- Prevent rotated environment keys from creating tokens during their grace period
- Limit realtime session writer authorization to the requested session channel
- Prevent public session access tokens from authorizing durable chat snapshot uploads
trigger.dev v4.6.1
Added 1
- Add new CLI commands: projects create/get/rename, runs list/get/replay/cancel, and env set
Changed 6
- Show schedule policy warnings during development and deployment with Free plan schedule limits displayed without internal stack traces
- Warn when a deployment uses the deprecated Node.js 21 runtime with upgrade guidance in deployment logs and email notification to the associated account
- Dashboard assistant now answers with investigation cards for run questions containing the run's timeline and links to the run, queue or deployment
- Dashboard assistant can answer questions about other projects or environments without requiring the user to switch to them first
- Deployments now show the runtime their worker actually reported instead of guessing, with Bun deployments no longer labeled as Node.js
- Deployments with no recorded runtime display a dash instead of a guess
Fixed 1
- Fix the MCP server failing every tools/list call with "Date cannot be represented in JSON Schema"
Deprecated 1
- Node.js 21 runtime is deprecated for deployments
trigger.dev v4.6.0
Added 4
- chat.agent now persists conversations through a TranscriptStorage adapter with load and save methods driven by the runtime after every turn
- chat.createLoadTranscriptAction and useLoadTranscript read conversations back consistently across different storage implementations
- runTranscriptStorageTests from @trigger.dev/sdk/ai/test validates TranscriptStorage implementations against the contract
- End a chat conversation from inside the agent with chat.close({ reason }) to close the session row and prevent further continuation scheduling
Changed 9
- Minimum supported Zod version is now 3.25.56, and Trigger.dev now uses Zod 4 by default while maintaining support for compatible Zod 3.x releases
- Reading a session's .in channel now requires a secret key; public tokens including read:sessions:{id} receive a 403 error
- The playwright build extension now works with Playwright 1.58 and later
- Automatically archive up to three inactive development branches when creating a branch at the plan limit, while protecting connected and recently active branches
- When the build log stream cannot be opened or disconnects during a deploy, the CLI now explains that deployment is unaffected and exits immediately with a non-zero code
- Build logs no longer include Docker's registry login output and credential-storage warnings
- Reduce sensitive values in CLI and SDK diagnostics, secure files created by trigger env pull, and remove credentials from collected Git remote metadata
- Compaction summaries and chat.inject context now survive continuation runs and crash recovery for every agent
- Snapshot format is now version 2, which older SDK versions cannot read
Fixed 2
- Failed writes to realtime or chat session streams no longer crash the process, and dropped chat session output writes are now logged
- A chat.agent run that recovers a session with multiple in-flight user messages no longer drops unanswered ones if it restarts mid-recovery
Deprecated 1
- hydrateMessages is deprecated in favour of loadContext on a storage
trigger.dev v4.5.16
Added 2
- The trigger.dev deploy and trigger.dev dev commands now warn with suggested fixes when your code loads a package through createRequire() that won't be available in the deployed image
- Deploys now show bundler warnings for your code instead of discarding them
Changed 1
- A durable guard improves reliability for runs waiting on triggerAndWait or batchTriggerAndWait if there's a database error that interrupts a child run finishing
Fixed 1
- Fix an issue introduced in 4.5.11 that made deploy image builds of projects with large dependency trees noticeably slower
Helm Chart 4.5.15
See commit history for detailed changes in this release.
Helm Chart 4.5.14
See commit history for detailed changes in this release.
Helm Chart 4.5.13
See commit history for detailed changes in this release.
trigger.dev v4.5.15
Added 1
- Named side channels on a Session for durable, two-way realtime streams that outlive a single run and are shared across runs, opened with sessions.open(id).channel(name) or chat.channel(name)
Changed 2
- Stop shipping compiled test files in the published packages to reduce package size and remove vitest dependency from tarballs
- Session triggerConfig.tags now accepts up to 10 tags instead of 5 to match the run tag limit
trigger.dev v4.5.14
Added 6
- Realtime stream subscriptions can now refresh an expired access token and reconnect via a new optional refreshAccessToken option on the client configuration and the React hooks
- Subscribe to a realtime stream from its latest record instead of replaying the whole history by passing from: "latest" to useRealtimeStream, streams.read(), or fetchStream to start at the current tail instead of replaying
- useRealtimeStream gains a lastEventId option and returns the lastEventId of the last part seen to persist the cursor and resume exactly where you left off
- useRealtimeStream supports maxParts to keep the accumulated parts array bounded
- useRealtimeStream gains an onParts callback that delivers each throttled batch of parts with their event ids
- Added a useSessionStream React hook for reading a session's output or input channel in realtime with automatic resume from the last record received
Changed 1
- Native build server deploys now show a single updating build log line by default; pass --build-logs full to stream every line (always used in CI and when output is not a terminal)
Fixed 1
- Task retries that wait in the queue no longer count against the queue's internal redelivery limit, preventing runs with many long-delay retries from being wrongly failed with TASK_RUN_DEQUEUED_MAX_RETRIES
trigger.dev v4.5.13
Added 3
- Add an experimental --local-bundle deploy flag that runs install and bundling steps on your machine and uploads only the build output while the image is built remotely
- Add chat.endAndContinue() to hand off a conversation to a fresh run on the latest deployed task version while preserving unconsumed Session input
- Custom agent loops can now inspect pending chat input without consuming it using chat.messages.hasPending() and chat.messages.next()
Changed 5
- trigger.dev deploy now asks the server whether to build with Depot or the native build server unless --native-build, --depot-build, or --local-build is passed, allowing per-organization rollout without CLI changes
- Send the CLI version header on all API requests so deployments are attributable to a CLI version
- Messages that arrive mid-turn and are not injected are now answered as the next turn instead of being dropped
- Browser chats now keep the active turn open across page reloads when older completion records are replayed
- Custom chat agents now validate and parse client data declared with chat.withClientData({ schema }) before passing it to agent code
Fixed 3
- Fix a case where a chat could silently lose a message if it arrived while the agent was between turns and a stop arrived after it
- Fix a recovered answer being cut off after a crash by only applying a stop to the turn that was live when it arrived
- Fix a retried send being answered twice when its idempotency claim was lost
Helm Chart 4.5.12
See commit history for detailed changes in this release.
trigger.dev v4.5.12
Added 4
- Define stable execution windows on declarative scheduled tasks with Schedule API responses now exposing both the nominal CRON time and its assigned time, and the dashboard showing configured windows and upcoming assignments
- Deploy with --external-id to tag a deployment with an id of your own such as a commit SHA, CI run id, or release tag so runs triggered by that release of your app go to that deployment
- List the current Production runtime for every accessible project with trigger projects list and use --needs-update to identify projects currently running Node.js 21
- Set TRIGGER_EXTERNAL_DEPLOYMENT_ID to pin runs to the deployment your calling code came from, or set TRIGGER_AUTOMATIC_SKEW_VERSION_PROTECTION=1 to detect the commit automatically on Vercel and most CI systems
Changed 7
- New projects created with trigger init use Node.js 24 by default
- Deployments without explicit runtime now use their project's configured default runtime
- Deployment builds now use custom base layer images and no longer install system packages during every build, improving layer caching for faster deployments and faster image pulls
- Unrelated runs are no longer merged into a single trace in external observability tools when they execute on the same warm worker process
- Dashboard pages load faster on projects with many preview branches by no longer loading every environment on each page
- Global log search now supports faster bounded substring matching and clearer time-range expansion
- Archiving a branch now returns you to the same page of the branches list, keeping your place, search and filters instead of resetting to the first page
Fixed 8
- Task metrics no longer go missing for projects that configure their own metricExporters or metricReaders, and the flush error that came with it is gone
- idempotencyKeys.reset() now works when your idempotency key is itself 64 characters long
- Fair queue tenants can no longer get permanently stuck behind leaked concurrency slots with slots now freed on every path that finishes a message
- Failed AI SDK tool call and embedding spans now show the error message and stack trace in the run inspector below the tool input
- A brief window after promoting or rolling back a deployment where newly triggered runs could still execute on the previous version is now fixed
- Using * as a concurrency key no longer stops a queue from being processed
- Root API keys no longer show an environment creation timestamp as their creation date
- Triggering tasks is now more resilient to brief, transient service interruptions so short stalls are less likely to surface as errors
Security 1
- Operators can now route an organization's runs to specific Kubernetes node pools
Helm Chart 4.5.8
See commit history for detailed changes in this release.
Helm Chart 4.5.9
See commit history for detailed changes in this release.
Helm Chart 4.5.10
See commit history for detailed changes in this release.
Helm Chart 4.5.11
See commit history for detailed changes in this release.
trigger.dev v4.5.11
Added 12
- Allow trigger deploy to authenticate with an environment API key from TRIGGER_ACCESS_TOKEN
- Chat in the browser now reconnects when the connection drops mid-turn instead of leaving the reply stuck as if it were still generating
- Reports can be fetched as structured data with the json format
- Dev environment onboarding now tracks real progress with live updates as the dev server connects and tasks register
- Setup checklist marks the project as initialized after running init
- Blank state adds a Copy AI agent prompt button that copies a ready-to-paste setup prompt pre-filled with your project reference
- The current-worker API now reports each task's queue so you can see which tasks write to a given queue
- Dashboard agent now has a monthly message allowance and plan-based limits on watches
- Introduced dashboard agent: a chat in every environment that answers questions about runs, queues, errors and health with real data and links
- Watch functionality on runs, queues, errors or health reports tells you when things change with notifications by email, Slack or webhook
- Queue wait times, peak depth, throughput and throttling can now be read from the API
- Add backend support for delaying cron schedules within a specified window with a minimum of 60 seconds
Changed 5
- The shortest report period is now one minute (1m, 30m, 1h, 7d)
- The mint-token command's help is clearer with --cap showing read-only behavior and --ttl showing the correct maximum lifetime of 7 days
- The init scaffold now imports from @trigger.dev/sdk instead of the deprecated @trigger.dev/sdk/v3 subpath
- Deployed images now ship dependencies and bundled task code as separate layers for faster deploys and worker image pulls
- Reduced recurring background database load from the billing-limit recovery check so paused environments are reconciled with less overhead
Fixed 3
- Watch-mode chat streams now survive quiet windows and page reloads
- A reply cut off by a lost connection now shows an error instead of appearing finished
- Project pages now load faster for projects with a large number of preview branches by no longer loading archived branch environments
trigger.dev v4.5.10
Added 7
- Allow task-scoped environment API keys to run batch operations for their permitted tasks
- Export additional-key format helper from @trigger.dev/core/v3/apiKeys
- Allow choosing the region a run executes in when triggering a task through the MCP server
- Allow self-hosted deployments to create multiple full-access API keys for each environment
- Short links like /_/apikeys now take you straight to that page in your current project and environment
- Additional environment API keys can now create scoped public access tokens
- Self-hosted Kubernetes deployments can now add tolerations to run pods
Changed 9
- Refresh package builds for TypeScript 7 compatibility while preserving existing runtime entry points
- AgentChat.reconnect() now settles promptly when reconnecting to an idle chat instead of holding the connection open for the full long-poll window
- Upgrade S2 streamstore client to 0.25 and move realtime streams to S2's current hosts
- Retry transient connection errors when a run starts for longer so a brief connectivity blip no longer delays its first attempt
- Dashboard gets a refreshed Dark theme as its new default look with Light, System preference, and Classic options available
- Additional environment API keys can authenticate API requests using their configured permissions with revoked and expired keys rejected
- Lower background database load during deployments and dev sessions for projects that use declarative schedules
- Triggering a task now does one fewer database write so runs reach the queue slightly faster
- Creating or updating a schedule and deploying a project with declarative schedules is faster in long-lived projects with many deploys
Fixed 3
- Fix debounce to work when passing an array of items to batchTrigger or batchTriggerAndWait and when triggering from useTaskTrigger
- Fix a chunk occasionally dropped when a chat.agent run takes over from the warm first turn
- Fix a preloaded chat.agent run dropping an in-flight message when it retries after an out-of-memory error
trigger.dev v4.5.9
Added 5
- trigger report health command returns a verdict on whether work is flowing, runs are succeeding, and telemetry is fresh enough to trust
- A queue's concurrency limit can now be set as a percentage of your environment limit from the dashboard or the API
- Queue metrics page shows backlog, throughput, concurrency against limit, throttling history, and run wait times, with per-concurrency-key breakdown on individual queue pages
- A queue's concurrency keys are now paged and searchable instead of limited to the busiest 50
- Self-hosted instances can now serve deployed runs' API traffic from a different origin than the public one per organization via the INTERNAL_API_ORIGIN environment variable
Changed 7
- Setting a queue concurrency limit higher than your environment limit is now rejected with an error instead of being silently reduced to the environment limit
- trigger mcp now always starts the MCP server, with the interactive install wizard moved behind trigger mcp --install
- Agent detail page now uses the same layout as other metrics pages with filters pinned at the top and resizable configuration panel on the right
- Prevent build debug logs from including environment variable values
- Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases
- People who are already in an organization are no longer sent invitations to it
- A query that fails is now recorded together with the query text that produced it
Fixed 5
- Correct the expirationTime docs on auth.createPublicToken and trigger-token helpers to clarify that a number is a Unix timestamp in seconds, not milliseconds
- Accepting an old invitation no longer changes the role of someone who was already in the organization
- Invite form now says which addresses it skipped instead of failing with an unhelpful error
- Fixed error reports being attributed to the wrong request when several requests were in flight at once
- Invalid queries sent to the query API are no longer treated as internal errors
Removed 1
- Removed an unused internal dashboard sync route
trigger.dev v4.5.8
Added 3
- Favorite any dashboard page to a new Favorites section in the side menu, and customize the sidebar by renaming favorites, hiding items, and reordering items and sections
- Add metrics to the realtime backend that measure how often a single changed run is served to multiple subscriptions in one batch
- Realtime run subscriptions can now be configured to read run data straight from the primary database instead of from a lagging replica, off by default
Changed 7
- Preserve the partial assistant message when a chat turn's model stream fails mid-response, passing the recovered partial to onTurnComplete and keeping it in chat.createSession before rethrowing
- List API endpoints now clamp the page size to a maximum of 100 items
- Organizations without billing alerts now get default spend alert thresholds, and the billing limit page no longer pre-selects an option and prompts configuration
- When creating a Personal Access Token, the generated token now shows its first and last few characters instead of being fully hidden
- SSO and Directory Sync are no longer restricted to Enterprise plans
- Improved supervisor observability with metrics for outbound requests to make failed calls to upstream services easier to monitor
- The runs list on a task's page now updates live with status changes and newly triggered runs appearing without manual refresh
Fixed 3
- Speed up the Batches list page for environments with a large number of batches that could previously time out while loading
- Container startup no longer prints database and ClickHouse connection strings with credentials to the logs
- The tasks page no longer runs two queries whose results were never displayed, removing wasted work on every page load and a source of hidden server errors
trigger.dev v4.5.7
Added 1
- Add node-24 and node-26 as supported runtime options in trigger.config.ts
Changed 8
- Avoid logging task run environment variable values at debug level
- chat.writeTurnComplete() now returns the turn boundary's resume cursors (lastEventId and sessionInEventId) for persistence from the task
- chat.pipeAndCapture() no longer throws when a stream is stopped or fails, instead returns a PipeAndCaptureResult with message, status, and error fields
- Suppress a build-time warning in Vite-based projects when the optional @ai-sdk/otel package is not installed
- Refresh the side menu with separate organization and account menus, new project switcher, and resizable edge
- Redesign the account Profile page
- Allow different organization members to use the same development branch name without sharing or colliding with each other's branch environments
- Limit account settings email input to 254 characters
Fixed 3
- Fix intermittent trigger dev run crashes with missing dev-run-worker.mjs by retrying cleanly when build directory is missing and providing clear messages for superseded worker versions
- Prevent duplicate Staging and Preview environments when account setup requests overlap
- Fix the docs link on the empty Prompts page that pointed to a page that no longer exists
Deprecated 1
- experimental-node-24 and experimental-node-26 runtime names are now deprecated aliases that emit a deprecation warning, use node-24 and node-26 instead
trigger.dev v4.5.6
Added 2
- Add helpers to mint and verify the deployment-scoped token used to authenticate run controllers to the platform
- Add optional request rate limiting for telemetry ingestion endpoints
Changed 1
- Deployed task telemetry now reports the deployment identifier in the worker.id attribute instead of an opaque internal value
Security 13
- Self-hosted deployments no longer ship shared default credentials; fresh installs generate their own
- Require explicit browser approval for CLI and MCP login, with resilient polling while approval is pending
- Prevent prototype pollution when applying run metadata operations or reconstructing nested telemetry attributes
- Background-worker deployment lookups are now scoped to the authenticated environment
- Updating a GitHub App installation from the callback flow is now scoped to your own organization
- GitHub App installation session is now single-use, invalidated after completing an installation callback
- Scope schedule and environment-variable writes to the caller's project and environment
- Reject compute snapshot callbacks that do not match the snapshot request that created them
- Require secret-key authentication to initialize the session out stream, matching the append route
- Live run and trace subscriptions now validate their identifiers more strictly and only return data from your own organization
- Window-function names in the query compiler are now validated against the allowlist
- Authenticate run controllers to the platform with a signed, deployment-scoped token
- Verify that worker actions target a run belonging to the caller's environment
trigger.dev v4.5.5
Added 2
- Add experimental Node.js 24 and 26 task runtimes via runtime option in trigger.config.ts
- Add defaultRegion to the project GET and list API responses
Changed 4
- Transient internal sync failures are now retried quietly instead of surfacing as errors
- Optionally route ClickHouse read traffic to a read replica while writes stay on the primary using CLICKHOUSE_READER_URL, RUNS_LIST_CLICKHOUSE_URL, or EVENTS_READER_CLICKHOUSE_URL
- Speed up idempotency checks on batchTrigger calls that use idempotency keys for large batches
- The Preview branches usage on the Limits page now counts only preview branches
Fixed 3
- Fix batchTrigger requests that set a per-item idempotency key failing with an error instead of creating and deduplicating the runs
- Fix pages occasionally loading unstyled or failing to load during a deploy by automatically reloading the dashboard
- Avoid opening a redundant database connection pool when the legacy and primary databases are the same server
Removed 1
- Remove the deprecated realtime stream write endpoint used by retired v3 task clients
trigger.dev v4.5.4
Added 5
- Mark environment variables synced via the syncEnvVars build extension as secrets by returning { name, value, isSecret: true } from your callback
- Add EVENT_REPOSITORY_POSTGRES_WRITES_DISABLED env var to skip all PostgreSQL task-event writes for deployments that store task events in ClickHouse
- Add promo credits feature with a /promo signup landing page, redeeming a promo code when a new org selects a plan, and showing remaining credits on the usage page
- Optionally process high-volume telemetry ingestion in parallel by setting OTEL_TRANSFORM_WORKER_POOL_ENABLED=1
- Add REALTIME_BACKEND_DEFAULT env var to choose the default realtime backend (electric, native, or shadow)
Changed 6
- Speed up retrieving a background worker by version by reusing already-loaded data instead of scanning the full task table
- Clarify login error message when an email address is blocked by WHITELISTED_EMAILS setting
- Make the native build server the default in project build settings, now opt-out with a disableNativeBuildServer key
- Clarify on the Regions page that a region only affects where runs execute, not where data is stored
- Improve the reliability of how run data is read and written
- Show better details on the Errors page with meaningful titles for errors without messages and grouping by error name
Fixed 4
- Fix a chat.agent message-loss race where sending a message right after an action could drop the follow-up's response from the UI until a refresh
- Fix stale login errors that reappear on the login page and make later successful attempts look like they failed
- Return a clear client error when SSO form submissions use an unsupported content type
- Fix Query page error when extracting fields from a run's output with JSON functions
Removed 4
- Trigger.dev v3 is no longer supported; v3 triggers, batch triggers, reschedules, and deploys now return a clear upgrade message instead of running
- Remove the legacy --mcp and --mcp-port options from the dev command in favor of the dedicated trigger mcp command
- Remove the unused ResourceMonitor export from @trigger.dev/core/v3/serverOnly
- Remove the unused @trigger.dev/core/v3/zodNamespace export and the legacy v3 socket message schemas
trigger.dev v4.5.3
Changed 1
- Reduce primary database load on the runs page by serving its empty-state check from ClickHouse instead of Postgres
Fixed 2
- Fix TS2742 (inferred type cannot be named) when exporting a chat.agent from a project with declaration emit by declaring ChatTaskWirePayload and ChatInputChunk in the public @trigger.dev/sdk/chat subpath
- Fixed submitting your email on the login page reloading back to an empty form instead of showing the magic link confirmation screen
Removed 1
- 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
trigger.dev v4.5.2
Added 2
- Bulk actions allow runs to be re-run based on a filter or run IDs via API and in the official SDK, supporting create, list, retrieve, poll and abort operations with targeting to different compute regions
- Add an onEvent callback to TriggerChatTransport and useTriggerChatTransport that emits typed lifecycle events for sends, stream connects, first chunk, and turn completion
Changed 7
- Large batch payloads now offload to object storage instead of riding inline in the trigger request, offloading any per-item payload over 128KB before sending
- The environment and branch selector dropdown will automatically revalidate when opened so that new branches show up
- Cleaner sign-in flow that requests a magic link right from the login page or continues with SSO
- Serve PostHog analytics from a same-origin /ph path that reverse-proxies to PostHog Cloud EU
- Refreshed the SSO & Directory Sync settings page layout and copy
- Migrated the webapp to Tailwind CSS v4 with a CSS-first @theme and semantic color tokens as CSS variables overridable per theme
- Replaced raw charcoal-* Tailwind classes with semantic theme tokens across the dashboard
Fixed 5
- Fix chat turns that throw from an onTurnStart hook leaking their message listener
- Fix chat.agent and chat.createSession permanently dropping user messages when several arrived during a single turn
- Fix chat continuation runs replaying already-answered messages by advancing the session.in resume cursor
- Fix chat.createSession swallowing a message sent shortly after stopping a turn
- Fix AI generation cost to use the exact provider-reported cost from OpenRouter/Vercel AI Gateway when present instead of catalog pricing
Removed 1
- Removed internal helpers that were only used by the end-of-life v3 self-hosted compute providers
Security 7
- Harden account and access-control handling across auth, RBAC, org membership, and impersonation
- Harden URL handling for alert webhooks and platform notifications
- Harden the query and prompt-override APIs and rate-limit the query ai-title endpoint
- Improve redaction of secrets from debug logs
- Tighten environment scoping when replaying a run
- Scope run, batch, and trigger lookups to the caller's tenant
- Honor the MCP server's --dev-only flag
trigger.dev v4.5.1
Changed 1
- Extend the SSO plugin contract with WorkOS Directory Sync (SCIM) support
More in Infrastructure & DevOps
View alln8n
Fair-code workflow automation, self-hosted or cloud.
n8n-io
Kubernetes
Production-grade container orchestration for automated deployment and scaling.
CNCF
frp
A fast reverse proxy that exposes a local server behind NAT or a firewall to the internet.
fatedier
Docker Engine
The container runtime that packages software into portable images.
Docker
Home Assistant
Open-source home automation that puts local control first.
Open Home Foundation
Ansible
A radically simple IT automation platform.
Red Hat
Discussion
If you publish Trigger.dev, you can claim this product by proving you administer its repository.