chore: release v4.7.3

[github-actions]

Summary

3 improvements, 4 bug fixes.

Breaking changes

• Creating or resuming a session with POST /api/v1/sessions now requires both session-write and task-trigger permissions. Scoped keys and public tokens must grant write:sessions (or access to the target session) and permission to trigger its task.

Improvements

• Reports filed with the submit_feedback MCP tool now reach the Trigger.dev team. They were being sent, but not somewhere anyone was reading. (4a94982a1)

• Stopping a chat.agent turn whose run() returns a streamText result no longer sends an error chunk with "An unexpected error occurred". The turn ends quietly again and the run stays alive for the next message. (64c3ba13c)

• chat.createStartSessionAction, chat.headStart and chat.startHeadStart now accept tags for the Session itself, so chat sessions can be filtered by tag on the Sessions page. triggerConfig.tags still tags the session's runs. (9dbc5f984)

  await startChatSession({
  chatId,
  clientData,
  tags: [`org:${org.slug}`, `user:${user.id}`],
  });

Server changes

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

• The Logs page loads and searches faster, and busy environments no longer fail to load it. Searches that are still too expensive now show a message suggesting a narrower range instead of a generic error.
• Fix a rare case where a run could stay stuck executing after the child run or wait it was waiting on had completed.
• Deployments with an unsupported runtime now fail with a 400 that names the supported runtimes, instead of a generic 500
• Preserve the cancellation reason when a run that was executing is finalized, instead of replacing it with the default text.

Raw changeset output

Releases

@trigger.dev/build@4.7.3

Patch Changes

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

trigger.dev@4.7.3

Patch Changes

• Reports filed with the submit_feedback MCP tool now reach the Trigger.dev team. They were being sent, but not somewhere anyone was reading. (4a94982a1)
• Updated dependencies:
  • @trigger.dev/build@4.7.3
  • @trigger.dev/core@4.7.3
  • @trigger.dev/schema-to-json@4.7.3

@trigger.dev/python@4.7.3

Patch Changes

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

@trigger.dev/react-hooks@4.7.3

Patch Changes

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

@trigger.dev/redis-worker@4.7.3

Patch Changes

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

@trigger.dev/rsc@4.7.3

Patch Changes

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

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

Patch Changes

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

@trigger.dev/sdk@4.7.3

Patch Changes

• Stopping a chat.agent turn whose run() returns a streamText result no longer sends an error chunk with "An unexpected error occurred". The turn ends quietly again and the run stays alive for the next message. (64c3ba13c)

• chat.createStartSessionAction, chat.headStart and chat.startHeadStart now accept tags for the Session itself, so chat sessions can be filtered by tag on the Sessions page. triggerConfig.tags still tags the session's runs. (9dbc5f984)

  await startChatSession({
    chatId,
    clientData,
    tags: [`org:${org.slug}`, `user:${user.id}`],
  });

• Updated dependencies:

  • @trigger.dev/core@4.7.3

@trigger.dev/core@4.7.3

[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: 7b7504fb-f38e-44ba-a2bf-3f8d8c1730e3

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

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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]

✅ Devin Review: No Issues Found

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