@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
4.8.8 is the newest release of 4.x.
In short
3 new1 fixed3 changed
Release note
trigger.dev v4.6.1
Warning
A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in package.json. Cold starts are unaffected by this bug. No data has been lost.
Redeploy with npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.6.1
Release notes
Read the full release notes: trigger.dev/changelog/v4-6-1
Improvements
Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces.
New CLI commands:
projects create/get/rename,runs list/get/replay/cancel, andenv setWarn 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.
Bug fixes
Fix the MCP server failing every
tools/listcall with "Date cannot be represented in JSON Schema"
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
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.
Warn when Production projects still use Node.js 21 and link directly to update instructions
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.
All packages: v4.6.1
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
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.