@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.7.4 to 4.7.5
1 release in betweenevery note read
Release by release
- New
Add
trigger.dev tasks trigger <task id>to trigger a task from your terminal. It uses the dev environment unless you pass--env, and--waitwaits for the run and prints its output or error, exiting with code 1 if it failed. Therunscommands now use the same dev branch astrigger devwhen you pass--env dev. - New
Manage custom metric dashboards from code.
query.dashboardslists, creates, updates and deletes custom dashboards and their widgets, and every widget query is checked when it is saved. The MCP server addscreate_dashboardandset_dashboard_widgets, so your AI assistant can build a dashboard for you. - New
trigger deployandtrigger promotenow say which environment they're targeting, and accept--prodas a shorthand for--env prod. WhenTRIGGER_ACCESS_TOKENholds an environment API key and you don't pass--env, they now use that key's environment instead of assuming prod. Passing an--envthat doesn't match the key is now an error, where before the deploy went to the key's environment. - New
trigger devworks better when a coding agent like Claude Code, Cursor or Codex runs it: it skips the install prompts, lists the tasks it registered, and prints each run's dashboard URL and output. For everyone, a failed build now ends with a line saying it will rebuild when you fix the errors, and retried attempts and crashed task processes now show their errors.
- New
8 other lines we could not sort, mostly version bumps
- 4.7.5
Update the @modelcontextprotocol/sdk dependency to ^1.31.0.
- 4.7.5
Recent deployments made with
--local-bundlecan now be redeployed from the deployments list, rebuilding the same bundle with its build-time environment variables. - 4.7.5
The API keys page now prompts you to create your first key instead of showing an empty table.
- 4.7.5
The short link /_/billing now takes you straight to the billing page of your current organization.
- 4.7.5
A
batchTriggerAndWaitcould stay stuck executing after all of its child runs finished, if creating the batch was retried while the server was slow to respond. The parent now resumes with its child runs' results. - 4.7.5
The natural-language field on the schedule form returns a cron expression again instead of an error.
- 4.7.5
Run traces returned by the API no longer include internal debug events.
- 4.7.5
A run whose process is killed is now only reported as out of memory when the machine actually ran out of memory. Any other kill (e.g. the machine being shut down or reclaimed) fails the attempt straight away as a crash, which is retried using your task's retry settings on the same machine size.
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.