@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.5.9 to 4.5.10
1 release in betweenevery note read
Release by release
- New
Allow task-scoped environment API keys to run batch operations for their permitted tasks. The SDK declares the batch's task set before creation, and
@trigger.dev/core/v3/apiKeysnow exports the additional-key format helper. - New
Refresh package builds for TypeScript 7 compatibility while preserving existing runtime entry points. Projects using
emitDecoratorMetadata()with TypeScript 7 can install the@typescript/typescript6compatibility package alongside it; the package remains optional, so installing the Trigger.dev CLI does not install an additional compiler. - New
AgentChat.reconnect()now settles promptly when reconnecting to an idle chat instead of holding the connection open for the full long-poll window. Also upgrades the S2 streamstore client to 0.25 and moves realtime streams to S2's current hosts. - New
You can now choose the region a run executes in when triggering a task through the MCP server.
- New
24 other lines we could not sort, mostly version bumps
- 4.5.10
Self-hosted deployments can now create multiple full-access API keys for each environment.
- 4.5.10
Short links like /_/apikeys now take you straight to that page in your current project and environment, so you no longer need the full URL with your org, project and environment in it.
- 4.5.10
The dashboard gets a refreshed Dark theme as its new default look. On the account page you can switch to Light, System preference (follows your OS), or the original Classic look, and fine-tune the new themes with a contrast slider.
- 4.5.10
Additional environment API keys can now create scoped public access tokens.
- 4.5.10
Additional environment API keys can authenticate API requests using their configured permissions, with revoked and expired keys rejected. Batch responses use server-issued public access tokens so additional keys never need the environment signing secret.
- 4.5.10
Self-hosted Kubernetes deployments can now add tolerations to run pods, so runs are allowed onto tainted nodes. An invalid toleration now stops the supervisor at startup instead of failing every run pod, so check existing values before upgrading.
- 4.5.10
Lower background database load during deployments and dev sessions for projects that use declarative schedules.
- 4.5.10
Triggering a task now does one fewer database write, so runs reach the queue slightly faster.
- 4.5.10
Creating or updating a schedule, and deploying a project with declarative schedules, is faster in long-lived projects with many deploys.
- 4.5.10
Admins opening an impersonation link from outside the dashboard now get a confirmation page naming the organization and destination instead of being bounced back, and while impersonating they can switch to "View as user" to see the dashboard exactly as that user sees it, with the admin-only UI and the impersonation highlight both hidden. Stopping impersonation is still one click away in the account menu.
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.