chore: release v4.5.9

[github-actions]

Summary

2 new features, 8 improvements, 4 bug fixes.

Breaking changes

• 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. (#4131)

Improvements

• trigger mcp now always starts the MCP server, and the interactive install wizard has moved behind trigger 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. (#4131)

• Ask whether an environment is healthy and get an answer instead of a wall of charts. trigger report health returns 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. (#4131)

  npx trigger.dev@latest report health --env prod --period 24h

  The verdict is computed server side, so the CLI, the new get_report MCP tool, and GET /api/v1/reports/health all return the same text with the same sparklines. In MCP hosts that support prompts, report is also available as a slash command.

• Prevent build debug logs from including environment variable values. (#4420)

• Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases. (#4407)

• Correct the expirationTime docs on auth.createPublicToken and the trigger-token helpers: a number is a Unix timestamp in seconds, not milliseconds. (#4388)

Server changes

These changes affect the self-hosted Docker image and Trigger.dev Cloud:

• 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. (#4131)
• 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. (#4131)
• 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. (#4131)
• Self-hosted instances can now serve deployed runs' API traffic from a different origin than the public one, per organization, via the INTERNAL_API_ORIGIN environment variable and a feature flag. (#4366)
• 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. (#4131)
• 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. (#4409)
• Removed an unused internal dashboard sync route that is no longer part of any product surface. (#4400)
• Fixed error reports being attributed to the wrong request when several requests were in flight at once. (#4372)
• 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. (#4372)

Raw changeset output

Releases

@trigger.dev/build@4.5.9

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.9

trigger.dev@4.5.9

Patch Changes

• trigger mcp now always starts the MCP server, and the interactive install wizard has moved behind trigger 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. (#4131)

• Ask whether an environment is healthy and get an answer instead of a wall of charts. trigger report health returns 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. (#4131)

  npx trigger.dev@latest report health --env prod --period 24h

  The verdict is computed server side, so the CLI, the new get_report MCP tool, and GET /api/v1/reports/health all return the same text with the same sparklines. In MCP hosts that support prompts, report is also available as a slash command.

• Prevent build debug logs from including environment variable values. (#4420)

• Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases. (#4407)

• Updated dependencies:

  • @trigger.dev/core@4.5.9
  • @trigger.dev/build@4.5.9
  • @trigger.dev/schema-to-json@4.5.9

@trigger.dev/core@4.5.9

Patch Changes

• Ask whether an environment is healthy and get an answer instead of a wall of charts. trigger report health returns 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. (#4131)

  npx trigger.dev@latest report health --env prod --period 24h

  The verdict is computed server side, so the CLI, the new get_report MCP tool, and GET /api/v1/reports/health all return the same text with the same sparklines. In MCP hosts that support prompts, report is also available as a slash command.

@trigger.dev/python@4.5.9

Patch Changes

• Updated dependencies:
  • @trigger.dev/sdk@4.5.9
  • @trigger.dev/core@4.5.9
  • @trigger.dev/build@4.5.9

@trigger.dev/react-hooks@4.5.9

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.9

@trigger.dev/redis-worker@4.5.9

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.9

@trigger.dev/rsc@4.5.9

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.9

@trigger.dev/schema-to-json@4.5.9

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.9

@trigger.dev/sdk@4.5.9

Patch Changes

• Correct the expirationTime docs on auth.createPublicToken and the trigger-token helpers: a number is a Unix timestamp in seconds, not milliseconds. (#4388)
• Updated dependencies:
  • @trigger.dev/core@4.5.9

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.