$
npx @buildinternet/releases get trigger-devRecently Shipped26 releases · updated Aug 24, 2026
Background tasks for long-running AI workloads got two scheduling additions in v4.5.12.
Scheduled tasks now support stable execution windows. Declarative scheduled tasks can define fixed execution windows; the Schedule API now exposes both the nominal CRON time and its assigned execution time. The dashboard surfaces configured windows alongside upcoming assignments, giving operators a clear picture of when tasks will actually run.
Deployments can carry external IDs. trigger.dev deploy --external-id tags a deployment with any identifier — a commit SHA, a CI run ID, or a release tag — so runs triggered by a given version of your app route to that deployment. Per-release tracing and rollbacks become straightforward without additional bookkeeping.
Durable chat agents persist across restarts. The chat.agent primitive maintains conversations in a Session that survives restarts and redeploys. chat.headStart runs the first LLM turn server-side while the agent boots, cutting cold start from 2801ms to 1218ms. AI SDK v7 (ESM-only) is supported alongside v5 and v6.
AI Prompts version templates without redeploying. Define with prompts.define({ id, model, config, variables, content }); every deploy snapshots the version. Dashboard overrides swap text or model per environment, and resolved.toAISDKTelemetry() links each span to its prompt version.
Tasks can reach private VPC resources directly. AWS PrivateLink support lets tasks connect to RDS, ElastiCache, and internal APIs without public endpoints. The platform holds HIPAA Business Associate compliance for workloads that process protected health information. Helm chart releases track each platform version for self-hosted deployments.
Trigger.dev Changelog · v4.7.4
Per-key concurrency overrides, much faster run traces for large and live runs, and runs.replay() options to change the payload and trigger settings on replay.
Trigger.dev Changelog · v4.7.3
Session creation now requires explicit trigger permissions, chat sessions support tags, and six server improvements including faster trace loading and Logs page performance.
Debug, investigate and generate reports on your runs by chatting with Ask Trigger from your dashboard.
Trigger.dev Changelog · v4.7.2
Node.js runtime defaults to LTS, chat.agent tool ordering fix, and a download fix for large payloads.
Trigger.dev Changelog · v4.7.1
Better trigger.dev init error handling and clearer authorization UX showing which account and organizations you're granting access to.
Trigger.dev Changelog · v4.7.0
Use multiple concurrency limits at once, restrict per-tenant concurrency with a total limit, and 4 bug fixes.
The Concurrency page now charts scheduling delay, backlog, and throttling for every queue and concurrency key, with live overrides and archiving for queues you no longer use.
Set a policy to archive preview branches once they go quiet. Choose how many days without a deployment, keep the branches you never want touched, and preview exactly what the next cleanup will retire.
Themes are here. Choose from Light, Dark, Black, and White, follow your system automatically, then tune contrast, colors, and links to make the dashboard work better for you.
Your app and your tasks deploy separately, so a fresh release can trigger tasks built from older code. Version skew protection pins every run to the deployment built from the same commit, across production, staging, and preview.
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…
Trigger.dev Changelog · v4.6.4
Fixes five-minute warm-start delays for projects using Zod 3.
Cap each tenant and the whole task at the same time, share one limit across many tasks with concurrencyLimit(), and change any limit at runtime without a deploy.