@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.5.8 to 4.5.9
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 5
- new
- 1
- fix
Before you upgrade
Tick each one off as you go- Breaking4.5.9
Release by release
- Breaking
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, so a queue never looks like it has more capacity than it can get. Limits already saved are unchanged.
- New
trigger mcpnow always starts the MCP server, and the interactive install wizard has moved behindtrigger mcp --install. Previously the wizard opened whenever stdout was a terminal, so any MCP host that spawns the command over a pseudo-terminal waited on a server that never started and eventually timed out. - New
Ask whether an environment is healthy and get an answer instead of a wall of charts.
trigger report healthreturns a verdict on three questions: is work flowing, are the runs that start succeeding, and is the telemetry fresh enough to trust either answer. When something looks wrong it names the most likely cause and a next action. - New
Prevent build debug logs from including environment variable values.
- New
Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases.
- New
Correct the
expirationTimedocs onauth.createPublicTokenand the trigger-token helpers: a number is a Unix timestamp in seconds, not milliseconds. - Fixed
Fixed error reports being attributed to the wrong request when several requests were in flight at once.
- Breaking
8 other lines we could not sort, mostly version bumps
- 4.5.9
A queue's concurrency limit can now be set as a percentage of your environment limit, from the dashboard or the API. Percentage limits track the environment limit, so raising or lowering it re-divides capacity without you editing every queue.
- 4.5.9
See how every queue in an environment is doing: backlog, throughput, concurrency against its limit, when it was throttled, and how long runs waited before starting. Each queue also gets its own page, which breaks the same numbers down per concurrency key so you can tell whether one key is starving the rest.
- 4.5.9
The agent detail page now uses the same layout as the other metrics pages: filters stay pinned at the top, the activity charts sit in a row beneath them, and the tabs and table scroll with the page, with the agent config in a resizable panel on the right.
- 4.5.9
Self-hosted instances can now serve deployed runs' API traffic from a different origin than the public one, per organization, via the
INTERNAL_API_ORIGINenvironment variable and a feature flag. - 4.5.9
A queue's concurrency keys are now paged and searchable, so a queue with thousands of keys shows all of them instead of only the busiest 50.
- 4.5.9
Accepting an old invitation could change the role of someone who was already in the organization. An invitation now leaves an existing member's role untouched, people who are already in an organization are no longer sent invitations to it, and the invite form now says which addresses it skipped instead of failing with an unhelpful error.
- 4.5.9
Removed an unused internal dashboard sync route that is no longer part of any product surface.
- 4.5.9
Invalid queries sent to the query API are no longer treated as internal errors, and a query that does fail is now recorded together with the query text that produced it.
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.