@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.5.5 to 4.5.6
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 0
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- Breaking4.5.6
Security
- 4.5.6
Require explicit browser approval for CLI and MCP login, with resilient polling while approval is pending.
- 4.5.6
Deployed task telemetry now reports the deployment identifier (e.g.
deployment_abc123) in theworker.idattribute, instead of an opaque internal value. Upgrade to get the readable identifier in your own OpenTelemetry exporters. - 4.5.6
Prevent prototype pollution when applying run metadata operations or reconstructing nested telemetry attributes, while preserving legitimate
constructorandprototypefields. - 4.5.6
Add helpers to mint and verify the deployment-scoped token used to authenticate run controllers to the platform.
- 4.5.6
Added optional request rate limiting for telemetry ingestion endpoints.
- 4.5.6
Background-worker deployment lookups are now scoped to the authenticated environment.
- 4.5.6
Updating a GitHub App installation from the callback flow is now scoped to your own organization, so an installation ID belonging to another organization can no longer be used to refresh that organization's installation record. The GitHub App installation session is also now single-use, so completing an installation callback invalidates its state and it can no longer be replayed.
- 4.5.6
Scope schedule and environment-variable writes to the caller's project and environment
- 4.5.6
Reject compute snapshot callbacks that do not match the snapshot request that created them.
- 4.5.6
Require secret-key authentication to initialize the session out (agent→client) stream, matching the append route.
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.