Tags: triggerdotdev/trigger.dev
Tags
chore: release v4.6.3 (#4945) ## Summary 3 improvements. ## Improvements - Show how to override the default cron window in schedule policy warnings. ([`630eb75d1`](630eb75)) - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Keep summarized assistant steps and tool results out of future `chat.agent()` model context after inner compaction, while preserving the full visible conversation. ([`fc77bfc9a`](fc77bfc)) <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## trigger.dev@4.6.3 ### Patch Changes - Show how to override the default cron window in schedule policy warnings. ([`630eb75d1`](630eb75)) - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Updated dependencies: - `@trigger.dev/core@4.6.3` - `@trigger.dev/build@4.6.3` - `@trigger.dev/schema-to-json@4.6.3` ## @trigger.dev/core@4.6.3 ### Patch Changes - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. ## @trigger.dev/python@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/sdk@4.6.3` - `@trigger.dev/core@4.6.3` - `@trigger.dev/build@4.6.3` ## @trigger.dev/react-hooks@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/redis-worker@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/rsc@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/schema-to-json@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/sdk@4.6.3 ### Patch Changes - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Keep summarized assistant steps and tool results out of future `chat.agent()` model context after inner compaction, while preserving the full visible conversation. ([`fc77bfc9a`](fc77bfc)) - Updated dependencies: - `@trigger.dev/core@4.6.3` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
chore: release v4.6.3 (#4945) ## Summary 3 improvements. ## Improvements - Show how to override the default cron window in schedule policy warnings. ([`630eb75d1`](630eb75)) - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Keep summarized assistant steps and tool results out of future `chat.agent()` model context after inner compaction, while preserving the full visible conversation. ([`fc77bfc9a`](fc77bfc)) <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## trigger.dev@4.6.3 ### Patch Changes - Show how to override the default cron window in schedule policy warnings. ([`630eb75d1`](630eb75)) - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Updated dependencies: - `@trigger.dev/core@4.6.3` - `@trigger.dev/build@4.6.3` - `@trigger.dev/schema-to-json@4.6.3` ## @trigger.dev/core@4.6.3 ### Patch Changes - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. ## @trigger.dev/python@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/sdk@4.6.3` - `@trigger.dev/core@4.6.3` - `@trigger.dev/build@4.6.3` ## @trigger.dev/react-hooks@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/redis-worker@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/rsc@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/schema-to-json@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/sdk@4.6.3 ### Patch Changes - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Keep summarized assistant steps and tool results out of future `chat.agent()` model context after inner compaction, while preserving the full visible conversation. ([`fc77bfc9a`](fc77bfc)) - Updated dependencies: - `@trigger.dev/core@4.6.3` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
perf(ci): balance internal tests across two runners Balance internal test files across packages and split the workload across two runners to reduce CI waits. Preserve package test configuration, refresh duration estimates, and combine all shard reports for timing updates. Mono-RevId: f43f740e7a8db6a812a157a8a02b2a15a7ac66fa
chore: release v4.6.3 (#4945) ## Summary 3 improvements. ## Improvements - Show how to override the default cron window in schedule policy warnings. ([`630eb75d1`](630eb75)) - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Keep summarized assistant steps and tool results out of future `chat.agent()` model context after inner compaction, while preserving the full visible conversation. ([`fc77bfc9a`](fc77bfc)) <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## trigger.dev@4.6.3 ### Patch Changes - Show how to override the default cron window in schedule policy warnings. ([`630eb75d1`](630eb75)) - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Updated dependencies: - `@trigger.dev/core@4.6.3` - `@trigger.dev/build@4.6.3` - `@trigger.dev/schema-to-json@4.6.3` ## @trigger.dev/core@4.6.3 ### Patch Changes - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. ## @trigger.dev/python@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/sdk@4.6.3` - `@trigger.dev/core@4.6.3` - `@trigger.dev/build@4.6.3` ## @trigger.dev/react-hooks@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/redis-worker@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/rsc@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/schema-to-json@4.6.3 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.3` ## @trigger.dev/sdk@4.6.3 ### Patch Changes - Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](4f36f61)) ```ts throw new Error("Could not sync the customer", { cause: originalError }); ``` The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks. - Keep summarized assistant steps and tool results out of future `chat.agent()` model context after inner compaction, while preserving the full visible conversation. ([`fc77bfc9a`](fc77bfc)) - Updated dependencies: - `@trigger.dev/core@4.6.3` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Publish docs: AI chat lifecycle-hooks + reference updates for the cha… …t.agent compaction change (v4.6.3)
chore: release v4.6.2 (#4942) ## Summary 5 improvements, 4 bug fixes. ## Improvements - Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads. ([`76031b0a1`](76031b0)) - Show warm idle time and durable waits separately in chat agent traces. Durable waits now open the waitpoint inspector while waiting and after completion. Message span names are shorter, and repeated session IDs no longer crowd message-wait and default output-stream spans. ([`0754931cc`](0754931)) - chat.agent: the between-turns compaction check now receives the last step's token usage (the context the model actually held) instead of the turn's sum over every tool-calling step, so a single tool-using turn no longer compacts a short conversation. The summed figure is still available as `turnUsage` on the event. A head-start handover whose pending tool call completes under the same message id now replaces its spliced partial in the model lane directly instead of falling back to a full reconversion. ([`04c837569`](04c8375)) - Validate resource IDs when creating scoped public tokens. Explicitly empty IDs are now rejected instead of being interpreted as type-wide permissions. ([`22f8fb2b5`](22f8fb2)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - The banner that prompts you to set a billing limit now lets you choose to run without one, so you don't have to open your billing limit settings to dismiss it. - Org member invites now match emails case-insensitively, so an invite whose email casing differs from the invitee's account email can be accepted. ([#3849](#3849)) - Limit public access tokens created through the JWT endpoint to the API key's permissions and a maximum 24-hour lifetime. Rotated environment keys can no longer create tokens during their grace period. - Realtime session writers now receive authorization limited to the requested session channel. - Prevent public session access tokens from authorizing durable chat snapshot uploads <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## trigger.dev@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` - `@trigger.dev/build@4.6.2` - `@trigger.dev/schema-to-json@4.6.2` ## @trigger.dev/core@4.6.2 ### Patch Changes - Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads. ([`76031b0a1`](76031b0)) ## @trigger.dev/python@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/sdk@4.6.2` - `@trigger.dev/core@4.6.2` - `@trigger.dev/build@4.6.2` ## @trigger.dev/react-hooks@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/redis-worker@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/rsc@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/schema-to-json@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/sdk@4.6.2 ### Patch Changes - Show warm idle time and durable waits separately in chat agent traces. Durable waits now open the waitpoint inspector while waiting and after completion. Message span names are shorter, and repeated session IDs no longer crowd message-wait and default output-stream spans. ([`0754931cc`](0754931)) - chat.agent: the between-turns compaction check now receives the last step's token usage (the context the model actually held) instead of the turn's sum over every tool-calling step, so a single tool-using turn no longer compacts a short conversation. The summed figure is still available as `turnUsage` on the event. A head-start handover whose pending tool call completes under the same message id now replaces its spliced partial in the model lane directly instead of falling back to a full reconversion. ([`04c837569`](04c8375)) - Validate resource IDs when creating scoped public tokens. Explicitly empty IDs are now rejected instead of being interpreted as type-wide permissions. ([`22f8fb2b5`](22f8fb2)) - Updated dependencies: - `@trigger.dev/core@4.6.2` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
chore: release v4.6.2 (#4942) ## Summary 5 improvements, 4 bug fixes. ## Improvements - Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads. ([`76031b0a1`](76031b0)) - Show warm idle time and durable waits separately in chat agent traces. Durable waits now open the waitpoint inspector while waiting and after completion. Message span names are shorter, and repeated session IDs no longer crowd message-wait and default output-stream spans. ([`0754931cc`](0754931)) - chat.agent: the between-turns compaction check now receives the last step's token usage (the context the model actually held) instead of the turn's sum over every tool-calling step, so a single tool-using turn no longer compacts a short conversation. The summed figure is still available as `turnUsage` on the event. A head-start handover whose pending tool call completes under the same message id now replaces its spliced partial in the model lane directly instead of falling back to a full reconversion. ([`04c837569`](04c8375)) - Validate resource IDs when creating scoped public tokens. Explicitly empty IDs are now rejected instead of being interpreted as type-wide permissions. ([`22f8fb2b5`](22f8fb2)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - The banner that prompts you to set a billing limit now lets you choose to run without one, so you don't have to open your billing limit settings to dismiss it. - Org member invites now match emails case-insensitively, so an invite whose email casing differs from the invitee's account email can be accepted. ([#3849](#3849)) - Limit public access tokens created through the JWT endpoint to the API key's permissions and a maximum 24-hour lifetime. Rotated environment keys can no longer create tokens during their grace period. - Realtime session writers now receive authorization limited to the requested session channel. - Prevent public session access tokens from authorizing durable chat snapshot uploads <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## trigger.dev@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` - `@trigger.dev/build@4.6.2` - `@trigger.dev/schema-to-json@4.6.2` ## @trigger.dev/core@4.6.2 ### Patch Changes - Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads. ([`76031b0a1`](76031b0)) ## @trigger.dev/python@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/sdk@4.6.2` - `@trigger.dev/core@4.6.2` - `@trigger.dev/build@4.6.2` ## @trigger.dev/react-hooks@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/redis-worker@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/rsc@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/schema-to-json@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/sdk@4.6.2 ### Patch Changes - Show warm idle time and durable waits separately in chat agent traces. Durable waits now open the waitpoint inspector while waiting and after completion. Message span names are shorter, and repeated session IDs no longer crowd message-wait and default output-stream spans. ([`0754931cc`](0754931)) - chat.agent: the between-turns compaction check now receives the last step's token usage (the context the model actually held) instead of the turn's sum over every tool-calling step, so a single tool-using turn no longer compacts a short conversation. The summed figure is still available as `turnUsage` on the event. A head-start handover whose pending tool call completes under the same message id now replaces its spliced partial in the model lane directly instead of falling back to a full reconversion. ([`04c837569`](04c8375)) - Validate resource IDs when creating scoped public tokens. Explicitly empty IDs are now rejected instead of being interpreted as type-wide permissions. ([`22f8fb2b5`](22f8fb2)) - Updated dependencies: - `@trigger.dev/core@4.6.2` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
chore: release v4.6.2 (#4942) ## Summary 5 improvements, 4 bug fixes. ## Improvements - Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads. ([`76031b0a1`](76031b0)) - Show warm idle time and durable waits separately in chat agent traces. Durable waits now open the waitpoint inspector while waiting and after completion. Message span names are shorter, and repeated session IDs no longer crowd message-wait and default output-stream spans. ([`0754931cc`](0754931)) - chat.agent: the between-turns compaction check now receives the last step's token usage (the context the model actually held) instead of the turn's sum over every tool-calling step, so a single tool-using turn no longer compacts a short conversation. The summed figure is still available as `turnUsage` on the event. A head-start handover whose pending tool call completes under the same message id now replaces its spliced partial in the model lane directly instead of falling back to a full reconversion. ([`04c837569`](04c8375)) - Validate resource IDs when creating scoped public tokens. Explicitly empty IDs are now rejected instead of being interpreted as type-wide permissions. ([`22f8fb2b5`](22f8fb2)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - The banner that prompts you to set a billing limit now lets you choose to run without one, so you don't have to open your billing limit settings to dismiss it. - Org member invites now match emails case-insensitively, so an invite whose email casing differs from the invitee's account email can be accepted. ([#3849](#3849)) - Limit public access tokens created through the JWT endpoint to the API key's permissions and a maximum 24-hour lifetime. Rotated environment keys can no longer create tokens during their grace period. - Realtime session writers now receive authorization limited to the requested session channel. - Prevent public session access tokens from authorizing durable chat snapshot uploads <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## trigger.dev@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` - `@trigger.dev/build@4.6.2` - `@trigger.dev/schema-to-json@4.6.2` ## @trigger.dev/core@4.6.2 ### Patch Changes - Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads. ([`76031b0a1`](76031b0)) ## @trigger.dev/python@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/sdk@4.6.2` - `@trigger.dev/core@4.6.2` - `@trigger.dev/build@4.6.2` ## @trigger.dev/react-hooks@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/redis-worker@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/rsc@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/schema-to-json@4.6.2 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.2` ## @trigger.dev/sdk@4.6.2 ### Patch Changes - Show warm idle time and durable waits separately in chat agent traces. Durable waits now open the waitpoint inspector while waiting and after completion. Message span names are shorter, and repeated session IDs no longer crowd message-wait and default output-stream spans. ([`0754931cc`](0754931)) - chat.agent: the between-turns compaction check now receives the last step's token usage (the context the model actually held) instead of the turn's sum over every tool-calling step, so a single tool-using turn no longer compacts a short conversation. The summed figure is still available as `turnUsage` on the event. A head-start handover whose pending tool call completes under the same message id now replaces its spliced partial in the model lane directly instead of falling back to a full reconversion. ([`04c837569`](04c8375)) - Validate resource IDs when creating scoped public tokens. Explicitly empty IDs are now rejected instead of being interpreted as type-wide permissions. ([`22f8fb2b5`](22f8fb2)) - Updated dependencies: - `@trigger.dev/core@4.6.2` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
chore: release v4.6.1 (#4936) ## Summary 1 new feature, 4 improvements, 2 bug fixes. ## Improvements - Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces. ([`723fde4a8`](723fde4)) - New CLI commands: `projects create/get/rename`, `runs list/get/replay/cancel`, and `env set` ([`5bcd1a9fa`](5bcd1a9)) - Warn when a deployment uses the deprecated Node.js 21 runtime. Deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification. ([`053b0b4c6`](053b0b4)) ## Bug fixes - Fix the MCP server failing every `tools/list` call with "Date cannot be represented in JSON Schema" ([`6c90639f2`](6c90639)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - The assistant in the dashboard now answers with cards: investigation cards for run questions, carrying the run's timeline and links to the run, queue or deployment, alongside charts and tables you can open fullscreen or copy — including queue metrics — and it answers about another project or environment without you switching to it first. The assistant reads run timelines through a dedicated endpoint, so span durations and launch events are consistent on every event store; the public run trace API is unchanged. - Warn when Production projects still use Node.js 21 and link directly to update instructions - Deployments now show the runtime their worker actually reported, so Bun deployments are no longer labelled Node.js; a deployment with no recorded runtime shows a dash instead of a guess. <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## trigger.dev@4.6.1 ### Patch Changes - Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces. ([`723fde4a8`](723fde4)) - New CLI commands: `projects create/get/rename`, `runs list/get/replay/cancel`, and `env set` ([`5bcd1a9fa`](5bcd1a9)) - Fix the MCP server failing every `tools/list` call with "Date cannot be represented in JSON Schema" ([`6c90639f2`](6c90639)) - Warn when a deployment uses the deprecated Node.js 21 runtime. Deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification. ([`053b0b4c6`](053b0b4)) - Updated dependencies: - `@trigger.dev/core@4.6.1` - `@trigger.dev/build@4.6.1` - `@trigger.dev/schema-to-json@4.6.1` ## @trigger.dev/core@4.6.1 ### Patch Changes - Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces. ([`723fde4a8`](723fde4)) ## @trigger.dev/python@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` - `@trigger.dev/build@4.6.1` - `@trigger.dev/sdk@4.6.1` ## @trigger.dev/react-hooks@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## @trigger.dev/redis-worker@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## @trigger.dev/rsc@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## @trigger.dev/schema-to-json@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## @trigger.dev/sdk@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
chore: release v4.6.1 (#4936) ## Summary 1 new feature, 4 improvements, 2 bug fixes. ## Improvements - Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces. ([`723fde4a8`](723fde4)) - New CLI commands: `projects create/get/rename`, `runs list/get/replay/cancel`, and `env set` ([`5bcd1a9fa`](5bcd1a9)) - Warn when a deployment uses the deprecated Node.js 21 runtime. Deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification. ([`053b0b4c6`](053b0b4)) ## Bug fixes - Fix the MCP server failing every `tools/list` call with "Date cannot be represented in JSON Schema" ([`6c90639f2`](6c90639)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - The assistant in the dashboard now answers with cards: investigation cards for run questions, carrying the run's timeline and links to the run, queue or deployment, alongside charts and tables you can open fullscreen or copy — including queue metrics — and it answers about another project or environment without you switching to it first. The assistant reads run timelines through a dedicated endpoint, so span durations and launch events are consistent on every event store; the public run trace API is unchanged. - Warn when Production projects still use Node.js 21 and link directly to update instructions - Deployments now show the runtime their worker actually reported, so Bun deployments are no longer labelled Node.js; a deployment with no recorded runtime shows a dash instead of a guess. <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## trigger.dev@4.6.1 ### Patch Changes - Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces. ([`723fde4a8`](723fde4)) - New CLI commands: `projects create/get/rename`, `runs list/get/replay/cancel`, and `env set` ([`5bcd1a9fa`](5bcd1a9)) - Fix the MCP server failing every `tools/list` call with "Date cannot be represented in JSON Schema" ([`6c90639f2`](6c90639)) - Warn when a deployment uses the deprecated Node.js 21 runtime. Deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification. ([`053b0b4c6`](053b0b4)) - Updated dependencies: - `@trigger.dev/core@4.6.1` - `@trigger.dev/build@4.6.1` - `@trigger.dev/schema-to-json@4.6.1` ## @trigger.dev/core@4.6.1 ### Patch Changes - Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces. ([`723fde4a8`](723fde4)) ## @trigger.dev/python@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` - `@trigger.dev/build@4.6.1` - `@trigger.dev/sdk@4.6.1` ## @trigger.dev/react-hooks@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## @trigger.dev/redis-worker@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## @trigger.dev/rsc@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## @trigger.dev/schema-to-json@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` ## @trigger.dev/sdk@4.6.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.6.1` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
PreviousNext