Packages

@trigger.dev/sdk

4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed

Upgrading @trigger.dev/sdk From 4.5.10 to 4.5.11

1 release in betweenevery note read

Other targets from 4.5.10Newest 4.x, Latest4.8.8
  1. 4.5.10yours
  2. 4.5.11target
0
changes to make
0
advisories fixed
9
new
4
fixes

Release by release

  1. 4.5.11

    13 Aug 20269 new · 4 fixes
    • New

      Allow trigger deploy to authenticate with an environment API key from TRIGGER_ACCESS_TOKEN.

    • New

      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 (1m, 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.

    • New

      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.

    • New

      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.

25 other lines we could not sort, mostly version bumps
  • The dashboard agent now has a monthly message allowance and plan-based limits on watches. Queries stay read-only with clearer errors when busy, and messages with unusual characters no longer fail to send.

    4.5.11
  • 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.

    4.5.11
  • Reduced recurring background database load from the billing-limit recovery check, so paused environments are reconciled with less overhead.

    4.5.11
  • Validating a schedule when deploying or updating a schedule now does less work on projects with many preview branches, so those operations stay fast as branches accumulate.

    4.5.11
  • Project pages now load faster for projects with a large number of preview branches, by no longer loading archived branch environments that aren't shown.

    4.5.11
  • 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.

    4.5.11
  • Routine cleanup of old dashboard agent data now runs on its own schedule.

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

    4.5.11
  • 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.

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

    4.5.11

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.