@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
4.8.8 is the newest release of 4.x.
In short
1 breaking5 new1 fixed5 changed
- Breaking
Creating or resuming a session with
POST /api/v1/sessionsnow requires both session-write and task-trigger permissions. Scoped keys and public tokens must grantwrite:sessions(or access to the target session) and permission to trigger its task.
Release note
trigger.dev v4.7.3
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.7.3
Release notes
Read the full release notes: trigger.dev/changelog/v4-7-3
Breaking changes
- Breaking
Creating or resuming a session with
POST /api/v1/sessionsnow requires both session-write and task-trigger permissions. Scoped keys and public tokens must grantwrite:sessions(or access to the target session) and permission to trigger its task.
Improvements
Update the minimatch dependency to ^10.2.3.
Add
trigger.dev orgs listto show the organizations you belong to, with their slugs and IDs. Use the slug withtrigger.dev projects create --org, including for organizations that don't have any projects yet.trigger.dev projects createnow activates the Free plan for organizations that don't have a plan yet, matchingtrigger.dev init.Reports filed with the
submit_feedbackMCP tool now reach the Trigger.dev team. They were being sent, but not somewhere anyone was reading.Stopping a
chat.agentturn whoserun()returns astreamTextresult no longer sends anerrorchunk with "An unexpected error occurred". The turn ends quietly again and the run stays alive for the next message.chat.createStartSessionAction,chat.headStartandchat.startHeadStartnow accepttagsfor the Session itself, so chat sessions can be filtered by tag on the Sessions page.triggerConfig.tagsstill tags the session's runs.await startChatSession({ chatId, clientData, tags: [`org:${org.slug}`, `user:${user.id}`], });
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Self-hosted instances can block sign-in and sign-up from specific email domains with the new
BLOCKED_EMAIL_DOMAINSsetting.Run traces now appear almost immediately and load progressively as you watch, and much larger traces are viewable than before.
The Logs page loads and searches faster, and busy environments no longer fail to load it. Searches that are still too expensive now show a message suggesting a narrower range instead of a generic error.
Fix a rare case where a run could stay stuck executing after the child run or wait it was waiting on had completed.
Deployments with an unsupported
runtimenow fail with a 400 that names the supported runtimes, instead of a generic 500Preserve the cancellation reason when a run that was executing is finalized, instead of replacing it with the default text.
All packages: v4.7.3
@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.