chore: release v4.5.10

[github-actions]

Summary

8 improvements, 5 bug fixes.

Improvements

• AgentChat.reconnect() now settles promptly when reconnecting to an idle chat instead of holding the connection open for the full long-poll window. Also upgrades the S2 streamstore client to 0.25 and moves realtime streams to S2's current hosts. (#4349)
• You can now choose the region a run executes in when triggering a task through the MCP server. (#4439)
• Transient connection errors when a run starts are now retried for longer, so a brief connectivity blip no longer sends the run back through the queue and delays its first attempt. (#4441)

Bug fixes

• Fix a chunk occasionally dropped when a chat.agent run takes over from the warm first turn. The realtime stream writer now reports the inclusive last-written position as the resume cursor, so the agent's first record after the handover is no longer skipped. (#4349)
• Fix a preloaded chat.agent run dropping an in-flight message when it retries after an out-of-memory error. The message being processed when the run hit the OOM is now recovered and re-run on the retry, instead of being skipped while the run waited for a new message. (#4349)

Server changes

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

• Triggering a task now does one fewer database write, so runs reach the queue slightly faster. (#4419)
• Admins opening an impersonation link from outside the dashboard now get a confirmation page naming the organization and destination instead of being bounced back, and while impersonating they can switch to "View as user" to see the dashboard exactly as that user sees it, with the admin-only UI and the impersonation highlight both hidden. Stopping impersonation is still one click away in the account menu. (#4421)
• In-app feedback and add-on/quota requests are now recorded with more account context for the support team. (#4368)
• Self-hosted Kubernetes deployments now measure running-task count more accurately when deciding whether to pause pulling new work, so the safeguard engages closer to its configured thresholds. (#4442)
• Speeds up resolving the latest worker version and deployment for an environment, removing an occasional stall when triggering runs in projects that have accumulated many deployed versions. (#4452)
• Batch triggers no longer fail to start their runs when an environment is under heavy API load. If a batch still can't finish being created, batchTriggerAndWait now fails with an error instead of leaving the parent run waiting forever, and the batches page says so rather than reporting that it resumed. (#4397)
• Fixed a rare case where a single run or span carrying data that could not be ingested would make other runs or trace events in the same batch go missing from the runs list, traces, and logs. Now the rest of the batch is always kept: an affected run still appears with its status (only its un-ingestable output is dropped), and an affected trace event or payload is skipped instead of taking down everything around it. (#4358)
• Team members who join an organization through single sign-on or directory sync now get their own development environment for every project, so the dashboard's dev view and trigger dev become available to them without an admin having to set anything up. Members who were already missing one are repaired the next time their membership is synced from your identity provider. (#4426)

Raw changeset output

Releases

@trigger.dev/build@4.5.10

Patch Changes

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

trigger.dev@4.5.10

Patch Changes

• AgentChat.reconnect() now settles promptly when reconnecting to an idle chat instead of holding the connection open for the full long-poll window. Also upgrades the S2 streamstore client to 0.25 and moves realtime streams to S2's current hosts. (#4349)
• You can now choose the region a run executes in when triggering a task through the MCP server. (#4439)
• Updated dependencies:
  • @trigger.dev/core@4.5.10
  • @trigger.dev/build@4.5.10
  • @trigger.dev/schema-to-json@4.5.10

@trigger.dev/core@4.5.10

Patch Changes

• Fix a chunk occasionally dropped when a chat.agent run takes over from the warm first turn. The realtime stream writer now reports the inclusive last-written position as the resume cursor, so the agent's first record after the handover is no longer skipped. (#4349)
• AgentChat.reconnect() now settles promptly when reconnecting to an idle chat instead of holding the connection open for the full long-poll window. Also upgrades the S2 streamstore client to 0.25 and moves realtime streams to S2's current hosts. (#4349)
• Transient connection errors when a run starts are now retried for longer, so a brief connectivity blip no longer sends the run back through the queue and delays its first attempt. (#4441)

@trigger.dev/python@4.5.10

Patch Changes

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

@trigger.dev/react-hooks@4.5.10

Patch Changes

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

@trigger.dev/redis-worker@4.5.10

Patch Changes

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

@trigger.dev/rsc@4.5.10

Patch Changes

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

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

Patch Changes

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

@trigger.dev/sdk@4.5.10

Patch Changes

• Fix a preloaded chat.agent run dropping an in-flight message when it retries after an out-of-memory error. The message being processed when the run hit the OOM is now recovered and re-run on the retry, instead of being skipped while the run waited for a new message. (#4349)
• AgentChat.reconnect() now settles promptly when reconnecting to an idle chat instead of holding the connection open for the full long-poll window. Also upgrades the S2 streamstore client to 0.25 and moves realtime streams to S2's current hosts. (#4349)
• Updated dependencies:
  • @trigger.dev/core@4.5.10

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

📝 Info: Deleted server-change notes are still recoverable for the release body

This release PR deletes all seven .server-changes/*.md files (via scripts/cleanup-server-changes.mjs, invoked from changeset:version in package.json:50). I checked whether those user-visible notes get lost: scripts/enhance-release-pr.mjs explicitly recovers deleted entries from the release-branch diff (getDeletedServerChangeFileDataFromReleaseBranch), merging them with any live files, so the "Server changes" section of the enhanced PR body / release notes still includes them even after cleanup. The plain changesets body shown in this PR description simply predates that enhancement step, so this is not a lost-notes bug.

---

Was this helpful? React with 👍 or 👎 to provide feedback.