Merge main into fix/chat-stop-successor-boundary

Author: gtremper

.changeset/calm-dates-listen.md

@@ -0,0 +1,5 @@
+---
+"@trigger.dev/schema-to-json": patch
+---
+
+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.

.changeset/chat-action-settlement.md

@@ -0,0 +1,5 @@
+---
+"@trigger.dev/sdk": patch
+---
+
+Add an optional `onSettled` callback to `TriggerChatTransport.sendAction()` so callers can confirm that their action's input was processed, independently of whether the response stream closes.

.changeset/chilly-plums-pause.md

@@ -0,0 +1,13 @@
+---
+"@trigger.dev/sdk": minor
+"@trigger.dev/core": minor
+---
+
+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.
+
+```ts
+import { concurrencyLimits } from "@trigger.dev/sdk";
+
+await concurrencyLimits.pause("openai");
+await concurrencyLimits.resume("openai");
+```

.changeset/deprecate-queue-concurrency-mutations.md

@@ -0,0 +1,5 @@
+---
+"@trigger.dev/sdk": patch
+---
+
+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.

.changeset/promote-environment-api-keys.md

@@ -0,0 +1,5 @@
+---
+"trigger.dev": patch
+---
+
+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.

.changeset/snapshot-route-zod-v4.md

@@ -0,0 +1,5 @@
+---
+"@trigger.dev/core": patch
+---
+
+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.

.oxlintrc.json

@@ -7,7 +7,8 @@
   "jsPlugins": [
     "./oxlint-plugins/no-thrown-unawaited-redirect.mjs",
     "./oxlint-plugins/runops-residency.mjs",
-    "./oxlint-plugins/prisma-in-filter.mjs"
+    "./oxlint-plugins/prisma-in-filter.mjs",
+    "./oxlint-plugins/zod-imports.mjs"
   ],
   "ignorePatterns": [
     "**/dist/**",
@@ -158,6 +159,12 @@
         "trigger-runops/no-control-plane-in-runops-slot": "error"
       }
     },
+    {
+      "files": ["packages/core/src/**/*.ts", "packages/core/src/**/*.tsx"],
+      "rules": {
+        "trigger-zod/require-versioned-import": "error"
+      }
+    },
     {
       "files": ["packages/react-hooks/src/**/*.ts", "packages/react-hooks/src/**/*.tsx"],
       "rules": {

.server-changes/2026-07-24-ck-fair-scheduling.md

@@ -0,0 +1,6 @@
+---
+area: webapp
+type: feature
+---
+
+One concurrency key with a large backlog no longer holds up runs waiting on other keys on the same queue.

.server-changes/api-rate-limit-metrics.md

@@ -0,0 +1,6 @@
+---
+area: webapp
+type: feature
+---
+
+API rate limit usage is now recorded per environment in the `metrics` table as `api.rate_limit.allowed`, `api.rate_limit.denied`, `api.rate_limit.remaining_min` and the limit itself (`api.rate_limit.limit.per_second` and `api.rate_limit.limit.burst`), so you can chart requests against your limit and 429s over time on the Query page and dashboards.

.server-changes/concurrency-allocation-hardening.md

@@ -0,0 +1,6 @@
+---
+area: webapp
+type: improvement
+---
+
+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.