Packages

@trigger.dev/sdk

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

Upgrading @trigger.dev/sdk From 4.6.0 to 4.6.1

1 release in betweenevery note read

Other targets from 4.6.0Newest 4.x, Latest4.8.8
  1. 4.6.0yours
  2. 4.6.1target
0
changes to make
0
advisories fixed
3
new
1
fix

Release by release

  1. 4.6.1

    15 Sep 20263 new · 1 fix
    • New

      Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces.

    • New

      New CLI commands: projects create/get/rename, runs list/get/replay/cancel, and env set

    • New

      Warn when a deployment uses the deprecated Node.js 21 runtime. Deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification.

    • Fixed

      Fix the MCP server failing every tools/list call with "Date cannot be represented in JSON Schema"

3 other lines we could not sort, mostly version bumps
  • The assistant in the dashboard now answers with cards: investigation cards for run questions, carrying the run's timeline and links to the run, queue or deployment, alongside charts and tables you can open fullscreen or copy — including queue metrics — and it answers about another project or environment without you switching to it first. The assistant reads run timelines through a dedicated endpoint, so span durations and launch events are consistent on every event store; the public run trace API is unchanged.

    4.6.1
  • Warn when Production projects still use Node.js 21 and link directly to update instructions

    4.6.1
  • Deployments now show the runtime their worker actually reported, so Bun deployments are no longer labelled Node.js; a deployment with no recorded runtime shows a dash instead of a guess.

    4.6.1

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.