@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.7.2 to 4.7.3
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 5
- new
- 1
- fix
Before you upgrade
Tick each one off as you go- Breaking4.7.3
Release by release
- 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. - New
Update the minimatch dependency to ^10.2.3.
- New
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. - New
Reports filed with the
submit_feedbackMCP tool now reach the Trigger.dev team. They were being sent, but not somewhere anyone was reading. - New
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. - New
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. - Fixed
Fix a rare case where a run could stay stuck executing after the child run or wait it was waiting on had completed.
- Breaking
5 other lines we could not sort, mostly version bumps
- 4.7.3
Self-hosted instances can block sign-in and sign-up from specific email domains with the new
BLOCKED_EMAIL_DOMAINSsetting. - 4.7.3
Run traces now appear almost immediately and load progressively as you watch, and much larger traces are viewable than before.
- 4.7.3
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.
- 4.7.3
Deployments with an unsupported
runtimenow fail with a 400 that names the supported runtimes, instead of a generic 500 - 4.7.3
Preserve the cancellation reason when a run that was executing is finalized, instead of replacing it with the default text.
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.