chore: release v4.5.0-rc.8

[github-actions]

Summary

2 new features, 7 improvements, 3 bug fixes.

Highlights

• Add support for dev branches to the webapp and CLI. This allows humans (and agents) to run multiple local dev servers simultaneously, with a separate dashboard for each one. (#4023)
• Add a redis_worker.queue.oldest_message_age observable gauge (unit ms, labeled worker_name) reporting the age of the oldest overdue message in each queue. This is a generic queue-stall signal: it stays at 0 while a queue drains healthily and rises only when due work sits undrained (e.g. a blocked dequeue, a dead consumer, or backpressure), even when no items are being processed. Orphaned queue entries are resolved against the items hash so they don't report a phantom stall. Also exposes SimpleQueue.oldestMessageAge(). (#4086)

Improvements

• Adds trigger.dev mint-token, which mints a short-lived delegated token from your stored personal access token. The token authenticates against the API as you, can be narrowed with --cap and given a lifetime with --ttl, and prints to stdout so it can be captured. (#3997)

  UAT=$(trigger.dev mint-token --ttl 3600 --cap read:runs)

• Runner debug logs are now disabled by default. Set SEND_RUN_DEBUG_LOGS=true on the supervisor to re-enable them. (#3992)

• Add request and response schemas for the new Errors API (error groups). These back the env-scoped HTTP endpoints for listing error groups, retrieving a single group, and changing its state (resolve, ignore, unresolve), plus a filter[error] option on the runs list to fetch the runs behind a group. Exported from @trigger.dev/core/v3 so the SDK can reuse them. (#4005)

• Add an optional skipBodyParsing flag to the internal HTTP server route definition, letting a route respond without reading or parsing the request body. (#4009)

• Redact credential-bearing flag values (e.g. --password, --token) from Exec command debug logs (#4087)

• chat.headStart now accepts an apiClient option (base URL + access token), so the head-start route can create the session and trigger the agent run against a different project/environment than the warm server's ambient Trigger config. Useful when your chat.agent lives in a separate project from the app serving the route. Mirrors the apiClient option on chat.createStartSessionAction; your LLM provider keys stay in the run callback and are unaffected. (#4018)

  export const POST = chat.headStart({
    agentId: "my-agent",
    apiClient: { baseURL, accessToken },
    run: async ({ chat }) =>
      streamText({
        ...chat.toStreamTextOptions({ tools }),
        model: anthropic("claude-sonnet-4-6"),
      }),
  });

• chat.createStartSessionAction now accepts an apiClient option, so you can scope a chat session start to a specific environment's API config (baseURL / accessToken) without setting a global TRIGGER_SECRET_KEY. Useful when one server starts chats across more than one environment. (#4018)

  const startSession = chat.createStartSessionAction("my-chat", {
    apiClient: { baseURL, accessToken },
  });
  
  await startSession({ chatId, clientData });

Bug fixes

• Fix idempotency key metadata (original key + scope) being silently dropped when a single run creates more than 1000 idempotency keys. The in-process catalog that maps a key's hash back to its original key/scope is no longer bounded to 1000 entries, so idempotencyKeys.create() results retain their metadata regardless of how many are created in a run. The catalog is now cleared at each run boundary so it does not accumulate across warm-start runs. (#4094)
• Fix chat.agent / AgentChat when the agent is deployed to a Trigger.dev preview branch. The realtime message-append and stream-subscribe calls now send the x-trigger-branch header (sourced from the same resolver sessions.start uses), so messaging a preview-branch chat agent no longer fails with x-trigger-branch header required for preview env. (#4018)
• Fix Head Start handovers breaking when a chat.agent also defines a prepareMessages hook. A handover hands the first turn's pending tool call to the agent as a tool-approval round whose trailing tool message must reach the model untouched. A prepareMessages hook that rewrites the last message (for example the recommended prompt-caching breakpoint) could disturb it, so the turn failed with "tool_use ids were found without tool_result". The agent now preserves that approval tail across prepareMessages, so caching and Head Start compose cleanly. (#4018)

Raw changeset output

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@trigger.dev/build@4.5.0-rc.8

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.8

trigger.dev@4.5.0-rc.8

Patch Changes

• Add support for dev branches to the webapp and CLI. This allows humans (and agents) to run multiple local dev servers simultaneously, with a separate dashboard for each one. (#4023)

• Fix idempotency key metadata (original key + scope) being silently dropped when a single run creates more than 1000 idempotency keys. The in-process catalog that maps a key's hash back to its original key/scope is no longer bounded to 1000 entries, so idempotencyKeys.create() results retain their metadata regardless of how many are created in a run. The catalog is now cleared at each run boundary so it does not accumulate across warm-start runs. (#4094)

• Adds trigger.dev mint-token, which mints a short-lived delegated token from your stored personal access token. The token authenticates against the API as you, can be narrowed with --cap and given a lifetime with --ttl, and prints to stdout so it can be captured. (#3997)

  UAT=$(trigger.dev mint-token --ttl 3600 --cap read:runs)

• Runner debug logs are now disabled by default. Set SEND_RUN_DEBUG_LOGS=true on the supervisor to re-enable them. (#3992)

• Updated dependencies:

  • @trigger.dev/core@4.5.0-rc.8
  • @trigger.dev/build@4.5.0-rc.8
  • @trigger.dev/schema-to-json@4.5.0-rc.8

@trigger.dev/core@4.5.0-rc.8

Patch Changes

• Add support for dev branches to the webapp and CLI. This allows humans (and agents) to run multiple local dev servers simultaneously, with a separate dashboard for each one. (#4023)
• Add request and response schemas for the new Errors API (error groups). These back the env-scoped HTTP endpoints for listing error groups, retrieving a single group, and changing its state (resolve, ignore, unresolve), plus a filter[error] option on the runs list to fetch the runs behind a group. Exported from @trigger.dev/core/v3 so the SDK can reuse them. (#4005)
• Add an optional skipBodyParsing flag to the internal HTTP server route definition, letting a route respond without reading or parsing the request body. (#4009)
• Fix idempotency key metadata (original key + scope) being silently dropped when a single run creates more than 1000 idempotency keys. The in-process catalog that maps a key's hash back to its original key/scope is no longer bounded to 1000 entries, so idempotencyKeys.create() results retain their metadata regardless of how many are created in a run. The catalog is now cleared at each run boundary so it does not accumulate across warm-start runs. (#4094)
• Redact credential-bearing flag values (e.g. --password, --token) from Exec command debug logs (#4087)

@trigger.dev/python@4.5.0-rc.8

Patch Changes

• Updated dependencies:
  • @trigger.dev/sdk@4.5.0-rc.8
  • @trigger.dev/core@4.5.0-rc.8
  • @trigger.dev/build@4.5.0-rc.8

@trigger.dev/react-hooks@4.5.0-rc.8

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.8

@trigger.dev/redis-worker@4.5.0-rc.8

Patch Changes

• Add a redis_worker.queue.oldest_message_age observable gauge (unit ms, labeled worker_name) reporting the age of the oldest overdue message in each queue. This is a generic queue-stall signal: it stays at 0 while a queue drains healthily and rises only when due work sits undrained (e.g. a blocked dequeue, a dead consumer, or backpressure), even when no items are being processed. Orphaned queue entries are resolved against the items hash so they don't report a phantom stall. Also exposes SimpleQueue.oldestMessageAge(). (#4086)
• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.8

@trigger.dev/rsc@4.5.0-rc.8

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.8

@trigger.dev/schema-to-json@4.5.0-rc.8

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.8

@trigger.dev/sdk@4.5.0-rc.8

Patch Changes

• Fix chat.agent / AgentChat when the agent is deployed to a Trigger.dev preview branch. The realtime message-append and stream-subscribe calls now send the x-trigger-branch header (sourced from the same resolver sessions.start uses), so messaging a preview-branch chat agent no longer fails with x-trigger-branch header required for preview env. (#4018)

• Fix Head Start handovers breaking when a chat.agent also defines a prepareMessages hook. A handover hands the first turn's pending tool call to the agent as a tool-approval round whose trailing tool message must reach the model untouched. A prepareMessages hook that rewrites the last message (for example the recommended prompt-caching breakpoint) could disturb it, so the turn failed with "tool_use ids were found without tool_result". The agent now preserves that approval tail across prepareMessages, so caching and Head Start compose cleanly. (#4018)

• chat.headStart now accepts an apiClient option (base URL + access token), so the head-start route can create the session and trigger the agent run against a different project/environment than the warm server's ambient Trigger config. Useful when your chat.agent lives in a separate project from the app serving the route. Mirrors the apiClient option on chat.createStartSessionAction; your LLM provider keys stay in the run callback and are unaffected. (#4018)

  export const POST = chat.headStart({
    agentId: "my-agent",
    apiClient: { baseURL, accessToken },
    run: async ({ chat }) =>
      streamText({
        ...chat.toStreamTextOptions({ tools }),
        model: anthropic("claude-sonnet-4-6"),
      }),
  });

• chat.createStartSessionAction now accepts an apiClient option, so you can scope a chat session start to a specific environment's API config (baseURL / accessToken) without setting a global TRIGGER_SECRET_KEY. Useful when one server starts chats across more than one environment. (#4018)

  const startSession = chat.createStartSessionAction("my-chat", {
    apiClient: { baseURL, accessToken },
  });
  
  await startSession({ chatId, clientData });

• Updated dependencies:

  • @trigger.dev/core@4.5.0-rc.8

@trigger.dev/plugins@4.5.0-rc.8

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.8

[devin-ai-integration]

✅ Devin Review: No Issues Found

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