chore: release v4.7.0

[github-actions]

Summary

2 new features, 10 improvements, 4 bug fixes.

Improvements

• Chat agents can now scope concurrency per session. Pass concurrencyKey (for example, your chat ID or tenant ID) and trigger-time named limits via triggerConfig.concurrency when starting a chat session, from chat.createStartSessionAction, the AgentChat client, or a handover. Keys are never defaulted, so a session without one shares the task's keyless pool. (ea9758117)

  const start = chat.createStartSessionAction("support-chat", {
  triggerConfig: { concurrencyKey: user.id },
  });

• Concurrency limits can now be paused and resumed, just like queues: concurrencyLimits.pause(name) stops every run holding the limit from being dequeued while keeping its configured bounds, and concurrencyLimits.resume(name) starts them again. (fa94febb6)

  import { concurrencyLimits } from "@trigger.dev/sdk";
  
  await concurrencyLimits.pause("openai");
  await concurrencyLimits.resume("openai");

• Control a task's concurrency with the new concurrency option, and share limits across tasks with named concurrency limits. An inline shape caps the task itself; concurrencyLimit() declares a limit any task can hold (up to two named limits per task), and a trigger call can switch a run's named limits with its own concurrency option. (ea9758117)

  import { concurrencyLimit, task } from "@trigger.dev/sdk";
  
  export const openaiLimit = concurrencyLimit({ name: "openai", total: 25 });
  
  export const generateSummary = task({
  id: "generate-summary",
  concurrency: [{ perKey: 1, total: 5 }, openaiLimit],
  run: async (payload) => {},
  });

  perKey caps each concurrencyKey pool and total caps across everything, keys or not. The queue-level concurrencyLimit option keeps working unchanged and is deprecated in favor of concurrency. Enforcement happens server-side; servers without support accept the option but do not enforce it yet.

  Manage limits at runtime with the new concurrencyLimits namespace: list() and retrieve(name) report each limit's bounds plus its live running and queued counts, override(name, { perKey, total }) changes only the given bounds (overriding total to 0 pauses the limit), and reset(name) restores the declared values.

  Queue reads (queues.list() and queues.retrieve()) now report a version that discriminates the shape: V1 queues keep today's fields (their own concurrencyLimit and its override state), while V2 queues (tasks declared with concurrency) carry no queue-level concurrency, since their limits are read and overridden through concurrencyLimits (a task's inline limit under its derived task/<task-id> name). Existing reads keep compiling: a V2 queue reports concurrencyLimit as null and concurrency as undefined.

• Chat streams now report Stream stalled: no records received after five retries of a connected stream that sends no records. Network failures and browser wakeups retain automatic recovery. Healthy tool calls with no records for about six minutes also reach this silence limit. Watch subscriptions remain unlimited, and caller cancellation still closes cleanly. (#4949)

• Webhook verifier artifacts can now declare the provider's response contract as data: a handshake respondStatus, the status codes returned for accepted deliveries and rejected signatures, and a GET verification flow (getHandshake) for providers that confirm a callback URL with a challenge. HMAC verifiers can read the timestamp from a body field, which the Linear provider config uses for its replay window, and the dashboard's test-send re-signs a recorded sample as of now so it passes that window. (5f54fb27f)

• Deprecate queues.overrideConcurrencyLimit and queues.resetConcurrencyLimit. These operate on the legacy model where a queue carried its own concurrency limit; declare concurrency with the task concurrency option and manage it with concurrencyLimits.override and concurrencyLimits.reset instead. (414e5a268)

• Steering messages now remain in context across agent steps and keep their original position in saved conversations, including custom response data written between steps. (5619acf26)

• Authenticate trigger promote with environment API keys supplied through TRIGGER_ACCESS_TOKEN. Environment API key commands now use the saved profile API URL when no explicit override is provided. (562c9433a)

• Convert Zod 4 z.date() fields to date-time strings in JSON Schema without weakening validation for other unsupported types. This prevents MCP tool discovery from failing when a tool input schema contains a date. (f8babdf9b)

Bug fixes

• Fix stale and empty project environment values in trigger dev, and support empty values in syncEnvVars(). (f384e8334)
• Fixes warm starts silently failing for deployments built with 4.6.0 to 4.6.3 in projects that resolve zod to a 3.x release. The runner could not parse the run handed to it by the warm-start service and exited, leaving the run waiting until the platform redrove it a few minutes later and started it cold. Redeploy to pick up the fix. (#4972)

Server changes

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

• Automatically archive preview branches after a configurable period without deployments, with protected branch names and a preview of affected branches.
• Download a session’s original saved transcript file from the session inspector.
• Allocating extra concurrency to environments now requires billing permissions, the same as purchasing it. Allocation changes are also applied atomically, so simultaneous edits can no longer exceed your purchased concurrency.
• Support empty-string environment values across the dashboard, API, and Vercel sync behind a feature flag, disabled by default.
• Team members and pending invites on the organization Team page are now listed in alphabetical order.

Raw changeset output

Releases

@trigger.dev/core@4.7.0

Minor Changes

• Chat agents can now scope concurrency per session. Pass concurrencyKey (for example, your chat ID or tenant ID) and trigger-time named limits via triggerConfig.concurrency when starting a chat session, from chat.createStartSessionAction, the AgentChat client, or a handover. Keys are never defaulted, so a session without one shares the task's keyless pool. (ea9758117)

  const start = chat.createStartSessionAction("support-chat", {
    triggerConfig: { concurrencyKey: user.id },
  });

• Concurrency limits can now be paused and resumed, just like queues: concurrencyLimits.pause(name) stops every run holding the limit from being dequeued while keeping its configured bounds, and concurrencyLimits.resume(name) starts them again. (fa94febb6)

  import { concurrencyLimits } from "@trigger.dev/sdk";
  
  await concurrencyLimits.pause("openai");
  await concurrencyLimits.resume("openai");

• Control a task's concurrency with the new concurrency option, and share limits across tasks with named concurrency limits. An inline shape caps the task itself; concurrencyLimit() declares a limit any task can hold (up to two named limits per task), and a trigger call can switch a run's named limits with its own concurrency option. (ea9758117)

  import { concurrencyLimit, task } from "@trigger.dev/sdk";
  
  export const openaiLimit = concurrencyLimit({ name: "openai", total: 25 });
  
  export const generateSummary = task({
    id: "generate-summary",
    concurrency: [{ perKey: 1, total: 5 }, openaiLimit],
    run: async (payload) => {},
  });

  perKey caps each concurrencyKey pool and total caps across everything, keys or not. The queue-level concurrencyLimit option keeps working unchanged and is deprecated in favor of concurrency. Enforcement happens server-side; servers without support accept the option but do not enforce it yet.

  Manage limits at runtime with the new concurrencyLimits namespace: list() and retrieve(name) report each limit's bounds plus its live running and queued counts, override(name, { perKey, total }) changes only the given bounds (overriding total to 0 pauses the limit), and reset(name) restores the declared values.

  Queue reads (queues.list() and queues.retrieve()) now report a version that discriminates the shape: V1 queues keep today's fields (their own concurrencyLimit and its override state), while V2 queues (tasks declared with concurrency) carry no queue-level concurrency, since their limits are read and overridden through concurrencyLimits (a task's inline limit under its derived task/<task-id> name). Existing reads keep compiling: a V2 queue reports concurrencyLimit as null and concurrency as undefined.

Patch Changes

• Fix stale and empty project environment values in trigger dev, and support empty values in syncEnvVars(). (f384e8334)
• Chat streams now report Stream stalled: no records received after five retries of a connected stream that sends no records. Network failures and browser wakeups retain automatic recovery. Healthy tool calls with no records for about six minutes also reach this silence limit. Watch subscriptions remain unlimited, and caller cancellation still closes cleanly. (#4949)
• Fixes warm starts silently failing for deployments built with 4.6.0 to 4.6.3 in projects that resolve zod to a 3.x release. The runner could not parse the run handed to it by the warm-start service and exited, leaving the run waiting until the platform redrove it a few minutes later and started it cold. Redeploy to pick up the fix. (#4972)
• Webhook verifier artifacts can now declare the provider's response contract as data: a handshake respondStatus, the status codes returned for accepted deliveries and rejected signatures, and a GET verification flow (getHandshake) for providers that confirm a callback URL with a challenge. HMAC verifiers can read the timestamp from a body field, which the Linear provider config uses for its replay window, and the dashboard's test-send re-signs a recorded sample as of now so it passes that window. (5f54fb27f)

@trigger.dev/react-hooks@4.7.0

Minor Changes

• Control a task's concurrency with the new concurrency option, and share limits across tasks with named concurrency limits. An inline shape caps the task itself; concurrencyLimit() declares a limit any task can hold (up to two named limits per task), and a trigger call can switch a run's named limits with its own concurrency option. (ea9758117)

  import { concurrencyLimit, task } from "@trigger.dev/sdk";
  
  export const openaiLimit = concurrencyLimit({ name: "openai", total: 25 });
  
  export const generateSummary = task({
    id: "generate-summary",
    concurrency: [{ perKey: 1, total: 5 }, openaiLimit],
    run: async (payload) => {},
  });

  perKey caps each concurrencyKey pool and total caps across everything, keys or not. The queue-level concurrencyLimit option keeps working unchanged and is deprecated in favor of concurrency. Enforcement happens server-side; servers without support accept the option but do not enforce it yet.

  Manage limits at runtime with the new concurrencyLimits namespace: list() and retrieve(name) report each limit's bounds plus its live running and queued counts, override(name, { perKey, total }) changes only the given bounds (overriding total to 0 pauses the limit), and reset(name) restores the declared values.

  Queue reads (queues.list() and queues.retrieve()) now report a version that discriminates the shape: V1 queues keep today's fields (their own concurrencyLimit and its override state), while V2 queues (tasks declared with concurrency) carry no queue-level concurrency, since their limits are read and overridden through concurrencyLimits (a task's inline limit under its derived task/<task-id> name). Existing reads keep compiling: a V2 queue reports concurrencyLimit as null and concurrency as undefined.

Patch Changes

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

@trigger.dev/sdk@4.7.0

Minor Changes

• Chat agents can now scope concurrency per session. Pass concurrencyKey (for example, your chat ID or tenant ID) and trigger-time named limits via triggerConfig.concurrency when starting a chat session, from chat.createStartSessionAction, the AgentChat client, or a handover. Keys are never defaulted, so a session without one shares the task's keyless pool. (ea9758117)

  const start = chat.createStartSessionAction("support-chat", {
    triggerConfig: { concurrencyKey: user.id },
  });

• Concurrency limits can now be paused and resumed, just like queues: concurrencyLimits.pause(name) stops every run holding the limit from being dequeued while keeping its configured bounds, and concurrencyLimits.resume(name) starts them again. (fa94febb6)

  import { concurrencyLimits } from "@trigger.dev/sdk";
  
  await concurrencyLimits.pause("openai");
  await concurrencyLimits.resume("openai");

• Control a task's concurrency with the new concurrency option, and share limits across tasks with named concurrency limits. An inline shape caps the task itself; concurrencyLimit() declares a limit any task can hold (up to two named limits per task), and a trigger call can switch a run's named limits with its own concurrency option. (ea9758117)

  import { concurrencyLimit, task } from "@trigger.dev/sdk";
  
  export const openaiLimit = concurrencyLimit({ name: "openai", total: 25 });
  
  export const generateSummary = task({
    id: "generate-summary",
    concurrency: [{ perKey: 1, total: 5 }, openaiLimit],
    run: async (payload) => {},
  });

  perKey caps each concurrencyKey pool and total caps across everything, keys or not. The queue-level concurrencyLimit option keeps working unchanged and is deprecated in favor of concurrency. Enforcement happens server-side; servers without support accept the option but do not enforce it yet.

  Manage limits at runtime with the new concurrencyLimits namespace: list() and retrieve(name) report each limit's bounds plus its live running and queued counts, override(name, { perKey, total }) changes only the given bounds (overriding total to 0 pauses the limit), and reset(name) restores the declared values.

  Queue reads (queues.list() and queues.retrieve()) now report a version that discriminates the shape: V1 queues keep today's fields (their own concurrencyLimit and its override state), while V2 queues (tasks declared with concurrency) carry no queue-level concurrency, since their limits are read and overridden through concurrencyLimits (a task's inline limit under its derived task/<task-id> name). Existing reads keep compiling: a V2 queue reports concurrencyLimit as null and concurrency as undefined.

Patch Changes

• Deprecate queues.overrideConcurrencyLimit and queues.resetConcurrencyLimit. These operate on the legacy model where a queue carried its own concurrency limit; declare concurrency with the task concurrency option and manage it with concurrencyLimits.override and concurrencyLimits.reset instead. (414e5a268)
• Chat streams now report Stream stalled: no records received after five retries of a connected stream that sends no records. Network failures and browser wakeups retain automatic recovery. Healthy tool calls with no records for about six minutes also reach this silence limit. Watch subscriptions remain unlimited, and caller cancellation still closes cleanly. (#4949)
• Steering messages now remain in context across agent steps and keep their original position in saved conversations, including custom response data written between steps. (5619acf26)
• Updated dependencies:
  • @trigger.dev/core@4.7.0

@trigger.dev/build@4.7.0

Patch Changes

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

trigger.dev@4.7.0

Patch Changes

• Fix stale and empty project environment values in trigger dev, and support empty values in syncEnvVars(). (f384e8334)
• Authenticate trigger promote with environment API keys supplied through TRIGGER_ACCESS_TOKEN. Environment API key commands now use the saved profile API URL when no explicit override is provided. (562c9433a)
• Updated dependencies:
  • @trigger.dev/schema-to-json@4.7.0
  • @trigger.dev/core@4.7.0
  • @trigger.dev/build@4.7.0

@trigger.dev/python@4.7.0

Patch Changes

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

@trigger.dev/redis-worker@4.7.0

Patch Changes

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

@trigger.dev/rsc@4.7.0

Patch Changes

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

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

Patch Changes

• Convert Zod 4 z.date() fields to date-time strings in JSON Schema without weakening validation for other unsupported types. This prevents MCP tool discovery from failing when a tool input schema contains a date. (f8babdf9b)
• Updated dependencies:
  • @trigger.dev/core@4.7.0

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: 66e16150-7493-4652-8c2f-e44634e133ac

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

✅ Devin Review: No Issues Found

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

[devin-ai-integration]

Devin Review found 1 new potential issue.

⚠️ 1 issue in files not directly in the diff

⚠️ Docker ignores the replication URL

Docker users setting WEBHOOK_DELIVERIES_REPLICATION_DATABASE_URL never pass it into the webapp container. Replication falls back to the pooled writer URL and cannot start.