chore: release v4.5.11

[github-actions]

Summary

1 new feature, 10 improvements, 2 bug fixes.

Improvements

• Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the json format, and the shortest report period is now one minute (30m, 1h, 7d). The mint-token command's help is clearer too: a token minted without --cap is read-only, and --ttl shows the correct maximum lifetime of 7 days. (#4418)

• The dev environment onboarding now tracks real progress. After you run init, the setup checklist marks your project as initialized, and it updates live as your dev server connects and your tasks register. The blank state also adds a "Copy AI agent prompt" button that copies a ready-to-paste setup prompt (pre-filled with your project reference) for Claude Code, Cursor, or any coding agent. (#4563)

  The init scaffold now imports from @trigger.dev/sdk instead of the deprecated @trigger.dev/sdk/v3 subpath.

• Deployed images now ship dependencies and bundled task code as separate layers. Repeat deploys with unchanged dependencies typically push and pull far less data, making deploys and worker image pulls faster. (#4551)

Server changes

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

• Meet the dashboard agent: a chat in every environment that answers questions about your runs, queues, errors and health with real data and links, replacing Ask AI everywhere it used to appear. Investigate a failed run, an error, a backed-up queue or a run that hasn't started to get a worked-through answer — what happened, why, and how to fix it, with every claim linked to the runs, errors and deploys behind it. It reads your data read-only, works on preview and dev branches with that branch's own data, and reads the same everywhere — dashboard, terminal, editor. A very long chat keeps working: the agent summarises the earlier part and carries on.

  A sample of conversations is scored automatically so the agent keeps getting better; only the score and a one-line summary are kept, never your messages, data or code, and we can switch it off for your organization on request. The Docs button is gone from page headers — ask the agent instead, or open Documentation from Help & Feedback. Separately, a queue's wait times, peak depth, throughput and throttling can now be read from the API. (#4418)

• Database queries that filter on a list of values now reuse cached query plans more consistently, instead of forcing the database to re-plan whenever the list length changes. (#4480)

• Database connection metrics are now reported for every configured database connection instead of only the primary one, and stay accurate regardless of connection type. (#4541)

• Deployment-related API endpoints now draw from their own generous rate limit budget, configurable via the DEPLOYMENT_RATE_LIMIT_* environment variables, so runtime API traffic no longer competes with deployments for the same per-environment budget. (#4565)

• Deleting or editing a secret environment variable is now fast and no longer slows down as a project accumulates variables. (#4555)

• Groundwork for an alternative database connection driver, gated behind configuration and disabled by default, so there is no change to default behavior. (#4539)

• Deleting an alert channel is now fast and no longer slows down as a project builds up alert history. (#4554)

• Reduced internal overhead on the API under high load. (#4532)

• Creating an organization sometimes left you back on the creation form even though the organization had already been created, so clicking Create again made a duplicate. Creating an organization now completes and takes you to your new organization. (#4530)

• The health report now says start latency is "unknown" when there is no data for it, instead of showing a healthy-looking 0ms (#4544)

Raw changeset output

Releases

@trigger.dev/build@4.5.11

Patch Changes

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

trigger.dev@4.5.11

Patch Changes

• Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the json format, and the shortest report period is now one minute (30m, 1h, 7d). The mint-token command's help is clearer too: a token minted without --cap is read-only, and --ttl shows the correct maximum lifetime of 7 days. (#4418)

• The dev environment onboarding now tracks real progress. After you run init, the setup checklist marks your project as initialized, and it updates live as your dev server connects and your tasks register. The blank state also adds a "Copy AI agent prompt" button that copies a ready-to-paste setup prompt (pre-filled with your project reference) for Claude Code, Cursor, or any coding agent. (#4563)

  The init scaffold now imports from @trigger.dev/sdk instead of the deprecated @trigger.dev/sdk/v3 subpath.

• Deployed images now ship dependencies and bundled task code as separate layers. Repeat deploys with unchanged dependencies typically push and pull far less data, making deploys and worker image pulls faster. (#4551)

• Updated dependencies:

  • @trigger.dev/core@4.5.11
  • @trigger.dev/build@4.5.11
  • @trigger.dev/schema-to-json@4.5.11

@trigger.dev/core@4.5.11

Patch Changes

• Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the json format, and the shortest report period is now one minute (30m, 1h, 7d). The mint-token command's help is clearer too: a token minted without --cap is read-only, and --ttl shows the correct maximum lifetime of 7 days. (#4418)

@trigger.dev/python@4.5.11

Patch Changes

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

@trigger.dev/react-hooks@4.5.11

Patch Changes

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

@trigger.dev/redis-worker@4.5.11

Patch Changes

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

@trigger.dev/rsc@4.5.11

Patch Changes

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

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

Patch Changes

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

@trigger.dev/sdk@4.5.11

Patch Changes

• Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the json format, and the shortest report period is now one minute (30m, 1h, 7d). The mint-token command's help is clearer too: a token minted without --cap is read-only, and --ttl shows the correct maximum lifetime of 7 days. (#4418)
• Updated dependencies:
  • @trigger.dev/core@4.5.11

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🔍 Consumed .server-changes entries are not reflected in the release PR summary

All ten .server-changes/*.md files are deleted in this release PR, but the PR body only lists package changesets. Per .server-changes/README.md ("The changeset release PR includes these in its summary; after the release merges, CI cleans up the consumed files"), those webapp notes should surface in the release summary before being removed. Worth confirming the release tooling actually captured them somewhere (e.g. a server release notes artifact), otherwise these user-facing server notes are silently dropped.

---

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