Packages

@trigger.dev/sdk

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

Upgrading @trigger.dev/sdk From 4.5.12 to 4.5.13

1 release in betweenevery note read

Other targets from 4.5.12Newest 4.x, Latest4.8.8
  1. 4.5.12yours
  2. 4.5.13target
1
change to make
0
advisories fixed
7
new
5
fixes

Before you upgrade

Tick each one off as you go
  • Deprecated4.5.13

Release by release

  1. 4.5.13

    Deprecation28 Aug 20267 new · 5 fixes
    • Deprecated

      New Vercel connections now get version skew protection turned on automatically, so each run uses the task version its deployment shipped with. Automatic atomic deployments are deprecated and no longer offered when you connect a project, but stay available in your Vercel integration settings.

    • New

      trigger.dev deploy now asks the server whether to build with Depot or the native build server unless --native-build, --depot-build, or --local-build is passed, so the native build server can be rolled out per organization without a CLI change. --local-bundle and --detach now require --native-build.

    • New

      Add an experimental --local-bundle deploy flag that runs the install and bundling steps on your machine and uploads only the build output; the image is still built remotely. Useful when your project's install step needs tooling or credentials that only exist locally.

    • New

      Send the CLI version header on all API requests so deployments are attributable to a CLI version

8 other lines we could not sort, mostly version bumps
  • Self-hosted instances can now disable the admin dashboard and user impersonation entirely. See the self-hosting docs for the new setting.

    4.5.13
  • The dashboard has two new themes, Black and White, plus appearance options for stronger colors and underlined links.

    4.5.13
  • Deployment logs no longer jump to the bottom while you are reading earlier output. Scroll up to pause auto-scroll, and scroll back down or use the new scroll-to-bottom button in the log header to resume following.

    4.5.13
  • Customize the runs list: show, hide, and reorder columns, and add smart columns that pull a value straight out of a run's payload, metadata, or output. Your column choices are saved in the page URL, so you can share a view, bookmark it, or save it straight to your favorites.

    4.5.13
  • Cut webapp CPU usage by about a quarter on the routes that workers call most, freeing headroom at the same request rate. Detailed event-loop blocking traces are no longer recorded by default, because producing them was itself a large part of that cost.

    4.5.13
  • When a runs list or runs.list API request spans too much data to complete, it now returns a clear, actionable error asking you to narrow the time range, instead of failing with a generic error.

    4.5.13
  • Improved the performance and reliability of the runs list and the runs.list API, especially for large projects and filtered views.

    4.5.13
  • The Staging branch setting now shows an upgrade prompt on plans that don't include a Staging environment, instead of looking editable and then silently doing nothing when saved.

    4.5.13

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.