@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.7.5 to 4.7.6
1 release in betweenevery note read
Release by release
- New
Added MCP tools for monitoring alerts:
list_alert_capabilities,list_alerts,create_alert, andresolve_alert, so an MCP client can discover what a project can watch and manage alerts directly. Health capabilities expose customizable threshold params, discoverable vialist_alert_capabilitiesand settable viacreate_alert. - New
Deploy images no longer trust the emSign roots removed after the October 2026 eMudhra CA key compromise, or the Sectigo AAA root that cross-signs the compromised intermediates. Node and Bun tasks now refuse TLS connections through the compromised eMudhra intermediates, including their Sectigo AAA cross-signed copies.
- New
NODE_EXTRA_CA_CERTSset as an environment variable now reaches the task process at startup instead of being overwritten by the image's empty default. - New
Python tasks and
pipin deploy images now verify TLS against the image's trust store instead of a pinned certifi bundle, so they also refuse the compromised eMudhra intermediates. - Fixed
Fix
timestampand otherDatefields being logged as{}in structured log lines.
- New
2 other lines we could not sort, mostly version bumps
- 4.7.6
Ask Trigger's message box is now a single panel holding your message, its context, New chat and Send, with a note that Ask Trigger is an AI assistant and can make mistakes. The chat header has a simpler layout menu and history list, and the Fullscreen layout is now called Full page.
- 4.7.6
The webapp Docker image no longer trusts the root certificates that chain to the compromised eMudhra intermediate CAs, so connections to servers presenting certificates from those intermediates now fail.
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.