Packages

@trigger.dev/sdk

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

Upgrading @trigger.dev/sdk From 4.5.16 to 4.6.0

1 release in betweenevery note read

Other targets from 4.5.16Newest 4.x, Latest4.8.8
  1. 4.5.16yours
  2. 4.6.0target

Before you upgrade

Tick each one off as you go
  • Breaking4.6.0
  • Breaking4.6.0
  • Breaking4.6.0
  • Deprecated4.6.0

Release by release

  1. 4.6.0

    Migration needed14 Sep 202633 new · 4 fixes
    • Breaking

      Minimum supported Zod version is now 3.25.56 released in June 2025. Trigger.dev now uses Zod 4 by default. Projects using Zod 3.25.56 or later 3.x releases remain supported. (#4039). Zod remains a runtime dependency of packages that execute schemas, so existing and new installations continue to receive it automatically. The matching peer dependency range allows package managers to reuse either a compatible Zod 3 or Zod 4 installation from your project.

    • Breaking

      Reading a session's .in channel (GET /realtime/v1/sessions/{id}/in and /in/records) now requires a secret key. Public tokens, including read:sessions:{id}, get a 403; they can still read .out and append to .in.

    • Breaking

      Returning a StreamTextResult, string or UIMessage from onAction is no longer supported and now fails with an error pointing to chat.turn().

    • Deprecated

      hydrateMessages is deprecated in favour of loadContext on a storage.

16 other lines we could not sort, mostly version bumps
  • Projects that need a Node.js runtime update can now be handed to a coding agent: the organization Projects settings page has a button that copies a ready-to-paste prompt listing every project to update.

    4.6.0
  • Additional API keys are now enabled by default. New environments no longer display root API keys, and existing environments can permanently disable their visibility

    4.6.0
  • Schedules now support a configurable minimum spread window that applies even when a smaller window is requested.

    4.6.0
  • The "Cancel in-progress runs when this limit is reached" option on the billing limit form is now enabled by default when you first configure a limit, so already-executing runs stop instead of continuing past the limit. Organizations that have already saved a billing limit keep their existing choice.

    4.6.0
  • Creating and archiving Development and Preview branches now requires the branch management permission, which the Developer role has by default.

    4.6.0
  • The assistant in the dashboard no longer has a monthly message limit, so you can chat with it as much as you like.

    4.6.0
  • Ask Trigger now opens as a floating window you can drag anywhere and resize, and the chat header lets you switch it to a right-side panel or fullscreen. Choose the position it opens in from your account settings.

    4.6.0
  • The Queues page Allocated tile now explains that it is the sum of your queue concurrency limits, and no longer shows a warning color when those add up to more than the environment limit, which is expected.

    4.6.0
  • Deleting a project now stops its pending runs. Runs that were waiting on a delay or sitting in the queue are cancelled instead of executing later, and a deleted project no longer sends task failure alerts.

    4.6.0
  • Dashboard pages no longer keep polling for updates while their browser tab is hidden, which could leave a tab you came back to showing a connection error instead of your data. Pages refresh when you return to the tab.

    4.6.0

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.