@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.5.11 to 4.5.12
1 release in betweenevery note read
Release by release
- New
Define stable execution windows on declarative scheduled tasks. Schedule API responses now expose both the nominal CRON time and its assigned time, while the dashboard shows configured windows and upcoming assignments.
- New
trigger.dev deploy --external-idtags a deployment with an id of your own — a commit SHA, a CI run id, a release tag — so runs triggered by that release of your app go to that deployment. Deploying an id that is already deployed builds nothing and reports the existing version instead of creating a duplicate; use--forceto rebuild it. - New
List the current Production runtime for every accessible project with
trigger projects list. Add--needs-updateto identify projects currently running Node.js 21. - New
New projects created with
trigger inituse Node.js 24 by default. Deployments without explicitruntimenow use their project's configured default runtime.
- New
15 other lines we could not sort, mostly version bumps
- 4.5.12
Deployments and runs now show the external ID they were deployed or pinned with, so you can trace a run back to the release of your app that triggered it.
- 4.5.12
Operators can now route an organization's runs to specific Kubernetes node pools.
- 4.5.12
Dashboard pages load faster on projects with many preview branches by no longer loading every environment on each page.
- 4.5.12
Global log search now supports faster bounded substring matching and clearer time-range expansion.
- 4.5.12
Triggering tasks is now more resilient to brief, transient service interruptions, so short stalls are less likely to surface as errors.
- 4.5.12
Failed AI SDK tool call and embedding spans now show the error message and stack trace in the run inspector, below the tool input.
- 4.5.12
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.
- 4.5.12
Using
*as a concurrency key no longer stops a queue from being processed. Triggering a single run with that key could leave the whole queue stalled, including runs using other concurrency keys on it, until something else was triggered on the same queue. - 4.5.12
Root API keys no longer show an environment creation timestamp as their creation date.
- 4.5.12
The app version shown on the organization settings page now reports the real version instead of v0.0.0.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.