chore: release v4.5.9 (#4408)
🚀 Publish Trigger.dev Docker / units (push) Failing after 0s
🚀 Publish Trigger.dev Docker / typecheck (push) Failing after 1s
🚀 Publish Trigger.dev Docker / publish-webapp (push) Has been skipped
🚀 Publish Trigger.dev Docker / publish-worker-v4 (push) Has been skipped
🚀 Publish Trigger.dev Docker / scan-webapp (push) Has been skipped
🚀 Publish Trigger.dev Docker / scan-supervisor (push) Has been skipped
🧭 Helm Chart Release / lint-and-test (push) Has been cancelled
🚀 Publish Trigger.dev Docker / 📣 Dispatch main image (push) Has been cancelled
🧭 Helm Chart Release / release (push) Has been cancelled

This commit is contained in:
github-actions[bot]
2026-07-30 10:12:14 +01:00
committed by GitHub
parent 6e5f0f0fe7
commit 86b948b47a
35 changed files with 121 additions and 129 deletions
@@ -1,5 +0,0 @@
---
"trigger.dev": patch
---
`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.
@@ -1,5 +0,0 @@
---
"@trigger.dev/sdk": patch
---
Correct the `expirationTime` docs on `auth.createPublicToken` and the trigger-token helpers: a number is a Unix timestamp in seconds, not milliseconds.
-12
View File
@@ -1,12 +0,0 @@
---
"@trigger.dev/core": patch
"trigger.dev": patch
---
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.
```bash
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.
-5
View File
@@ -1,5 +0,0 @@
---
"trigger.dev": patch
---
Prevent build debug logs from including environment variable values.
-5
View File
@@ -1,5 +0,0 @@
---
"trigger.dev": patch
---
Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases.
@@ -1,6 +0,0 @@
---
area: webapp
type: improvement
---
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.
@@ -1,6 +0,0 @@
---
area: webapp
type: fix
---
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.
@@ -1,6 +0,0 @@
---
area: webapp
type: improvement
---
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.
@@ -1,6 +0,0 @@
---
area: webapp
type: improvement
---
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.
@@ -1,6 +0,0 @@
---
area: webapp
type: feature
---
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.
@@ -1,6 +0,0 @@
---
area: webapp
type: feature
---
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.
@@ -1,6 +0,0 @@
---
area: webapp
type: 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.
@@ -1,6 +0,0 @@
---
area: webapp
type: fix
---
Removed an unused internal dashboard sync route that is no longer part of any product surface.
@@ -1,6 +0,0 @@
---
area: webapp
type: fix
---
Fixed error reports being attributed to the wrong request when several requests were in flight at once.
@@ -1,6 +0,0 @@
---
area: webapp
type: fix
---
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.
+2 -2
View File
@@ -2,8 +2,8 @@ apiVersion: v2
name: trigger
description: The official Trigger.dev Helm chart
type: application
version: 4.5.8
appVersion: v4.5.8
version: 4.5.9
appVersion: v4.5.9
home: https://trigger.dev
sources:
- https://github.com/triggerdotdev/trigger.dev
+7
View File
@@ -1,5 +1,12 @@
# @trigger.dev/build
## 4.5.9
### Patch Changes
- Updated dependencies:
- `@trigger.dev/core@4.5.9`
## 4.5.8
### Patch Changes
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/build",
"version": "4.5.8",
"version": "4.5.9",
"description": "trigger.dev build extensions",
"license": "MIT",
"publishConfig": {
@@ -79,7 +79,7 @@
},
"dependencies": {
"@prisma/config": "^6.10.0",
"@trigger.dev/core": "workspace:4.5.8",
"@trigger.dev/core": "workspace:4.5.9",
"mlly": "^1.7.1",
"pkg-types": "^1.1.3",
"resolve": "^1.22.8",
+20
View File
@@ -1,5 +1,25 @@
# 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](https://github.com/triggerdotdev/trigger.dev/pull/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](https://github.com/triggerdotdev/trigger.dev/pull/4131))
```bash
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](https://github.com/triggerdotdev/trigger.dev/pull/4420))
- Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases. ([#4407](https://github.com/triggerdotdev/trigger.dev/pull/4407))
- Updated dependencies:
- `@trigger.dev/core@4.5.9`
- `@trigger.dev/build@4.5.9`
- `@trigger.dev/schema-to-json@4.5.9`
## 4.5.8
### Patch Changes
+4 -4
View File
@@ -1,6 +1,6 @@
{
"name": "trigger.dev",
"version": "4.5.8",
"version": "4.5.9",
"description": "A Command-Line Interface for Trigger.dev projects",
"type": "module",
"license": "MIT",
@@ -96,9 +96,9 @@
"@opentelemetry/sdk-trace-node": "2.7.1",
"@opentelemetry/semantic-conventions": "1.41.1",
"@s2-dev/streamstore": "^0.22.10",
"@trigger.dev/build": "workspace:4.5.8",
"@trigger.dev/core": "workspace:4.5.8",
"@trigger.dev/schema-to-json": "workspace:4.5.8",
"@trigger.dev/build": "workspace:4.5.9",
"@trigger.dev/core": "workspace:4.5.9",
"@trigger.dev/schema-to-json": "workspace:4.5.9",
"ansi-escapes": "^7.0.0",
"braces": "^3.0.3",
"c12": "^1.11.1",
+12
View File
@@ -1,5 +1,17 @@
# internal-platform
## 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](https://github.com/triggerdotdev/trigger.dev/pull/4131))
```bash
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.
## 4.5.8
### Patch Changes
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/core",
"version": "4.5.8",
"version": "4.5.9",
"description": "Core code used across the Trigger.dev SDK and platform",
"license": "MIT",
"publishConfig": {
+9
View File
@@ -1,5 +1,14 @@
# @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`
## 4.5.8
### Patch Changes
+6 -6
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/python",
"version": "4.5.8",
"version": "4.5.9",
"description": "Python runtime and build extension for Trigger.dev",
"license": "MIT",
"publishConfig": {
@@ -45,7 +45,7 @@
"check-exports": "attw --pack ."
},
"dependencies": {
"@trigger.dev/core": "workspace:4.5.8",
"@trigger.dev/core": "workspace:4.5.9",
"tinyexec": "^0.3.2"
},
"devDependencies": {
@@ -56,12 +56,12 @@
"tsx": "4.17.0",
"esbuild": "^0.23.0",
"@arethetypeswrong/cli": "^0.18.5",
"@trigger.dev/build": "workspace:4.5.8",
"@trigger.dev/sdk": "workspace:4.5.8"
"@trigger.dev/build": "workspace:4.5.9",
"@trigger.dev/sdk": "workspace:4.5.9"
},
"peerDependencies": {
"@trigger.dev/sdk": "workspace:^4.5.8",
"@trigger.dev/build": "workspace:^4.5.8"
"@trigger.dev/sdk": "workspace:^4.5.9",
"@trigger.dev/build": "workspace:^4.5.9"
},
"engines": {
"node": ">=18.20.0"
+7
View File
@@ -1,5 +1,12 @@
# @trigger.dev/react-hooks
## 4.5.9
### Patch Changes
- Updated dependencies:
- `@trigger.dev/core@4.5.9`
## 4.5.8
### Patch Changes
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/react-hooks",
"version": "4.5.8",
"version": "4.5.9",
"description": "trigger.dev react hooks",
"license": "MIT",
"publishConfig": {
@@ -37,7 +37,7 @@
"check-exports": "attw --pack ."
},
"dependencies": {
"@trigger.dev/core": "workspace:^4.5.8",
"@trigger.dev/core": "workspace:^4.5.9",
"swr": "^2.2.5"
},
"devDependencies": {
+7
View File
@@ -1,5 +1,12 @@
# @trigger.dev/redis-worker
## 4.5.9
### Patch Changes
- Updated dependencies:
- `@trigger.dev/core@4.5.9`
## 4.5.8
### Patch Changes
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/redis-worker",
"version": "4.5.8",
"version": "4.5.9",
"description": "Redis worker for trigger.dev",
"license": "MIT",
"publishConfig": {
@@ -23,7 +23,7 @@
"test": "vitest --sequence.concurrent=false --no-file-parallelism"
},
"dependencies": {
"@trigger.dev/core": "workspace:4.5.8",
"@trigger.dev/core": "workspace:4.5.9",
"lodash.omit": "^4.5.0",
"nanoid": "^5.0.7",
"p-limit": "^6.2.0",
+7
View File
@@ -1,5 +1,12 @@
# @trigger.dev/rsc
## 4.5.9
### Patch Changes
- Updated dependencies:
- `@trigger.dev/core@4.5.9`
## 4.5.8
### Patch Changes
+3 -3
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/rsc",
"version": "4.5.8",
"version": "4.5.9",
"description": "trigger.dev rsc",
"license": "MIT",
"publishConfig": {
@@ -37,14 +37,14 @@
"check-exports": "attw --pack ."
},
"dependencies": {
"@trigger.dev/core": "workspace:^4.5.8",
"@trigger.dev/core": "workspace:^4.5.9",
"mlly": "^1.7.1",
"react": "19.0.0-rc.1",
"react-dom": "19.0.0-rc.1"
},
"devDependencies": {
"@arethetypeswrong/cli": "^0.18.5",
"@trigger.dev/build": "workspace:^4.5.8",
"@trigger.dev/build": "workspace:^4.5.9",
"@types/node": "^24.13.3",
"@types/react": "*",
"@types/react-dom": "*",
+7
View File
@@ -1,5 +1,12 @@
# @trigger.dev/schema-to-json
## 4.5.9
### Patch Changes
- Updated dependencies:
- `@trigger.dev/core@4.5.9`
## 4.5.8
### Patch Changes
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/schema-to-json",
"version": "4.5.8",
"version": "4.5.9",
"description": "Convert various schema validation libraries to JSON Schema",
"license": "MIT",
"publishConfig": {
+8
View File
@@ -1,5 +1,13 @@
# @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](https://github.com/triggerdotdev/trigger.dev/pull/4388))
- Updated dependencies:
- `@trigger.dev/core@4.5.9`
## 4.5.8
### Patch Changes
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "@trigger.dev/sdk",
"version": "4.5.8",
"version": "4.5.9",
"description": "trigger.dev Node.JS SDK",
"license": "MIT",
"publishConfig": {
@@ -77,7 +77,7 @@
"dependencies": {
"@opentelemetry/api": "1.9.1",
"@opentelemetry/semantic-conventions": "1.41.1",
"@trigger.dev/core": "workspace:4.5.8",
"@trigger.dev/core": "workspace:4.5.9",
"chalk": "^5.2.0",
"cronstrue": "^2.21.0",
"debug": "^4.3.4",
+12 -12
View File
@@ -1450,7 +1450,7 @@ importers:
specifier: ^6.10.0
version: 6.19.0(magicast@0.3.5)
'@trigger.dev/core':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../core
mlly:
specifier: ^1.7.1
@@ -1526,13 +1526,13 @@ importers:
specifier: ^0.22.10
version: 0.22.10(supports-color@10.0.0)
'@trigger.dev/build':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../build
'@trigger.dev/core':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../core
'@trigger.dev/schema-to-json':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../schema-to-json
ansi-escapes:
specifier: ^7.0.0
@@ -1919,7 +1919,7 @@ importers:
packages/python:
dependencies:
'@trigger.dev/core':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../core
tinyexec:
specifier: ^0.3.2
@@ -1929,10 +1929,10 @@ importers:
specifier: ^0.18.5
version: 0.18.5
'@trigger.dev/build':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../build
'@trigger.dev/sdk':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../trigger-sdk
'@types/node':
specifier: 24.13.3
@@ -1956,7 +1956,7 @@ importers:
packages/react-hooks:
dependencies:
'@trigger.dev/core':
specifier: workspace:^4.5.8
specifier: workspace:^4.5.9
version: link:../core
react:
specifier: 18.3.1
@@ -1990,7 +1990,7 @@ importers:
packages/redis-worker:
dependencies:
'@trigger.dev/core':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../core
cron-parser:
specifier: ^4.9.0
@@ -2039,7 +2039,7 @@ importers:
packages/rsc:
dependencies:
'@trigger.dev/core':
specifier: workspace:^4.5.8
specifier: workspace:^4.5.9
version: link:../core
mlly:
specifier: ^1.7.1
@@ -2055,7 +2055,7 @@ importers:
specifier: ^0.18.5
version: 0.18.5
'@trigger.dev/build':
specifier: workspace:^4.5.8
specifier: workspace:^4.5.9
version: link:../build
'@types/node':
specifier: 24.13.3
@@ -2134,7 +2134,7 @@ importers:
specifier: 1.41.1
version: 1.41.1
'@trigger.dev/core':
specifier: workspace:4.5.8
specifier: workspace:4.5.9
version: link:../core
chalk:
specifier: ^5.2.0