@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 breaking14 security
- Breaking
Self-hosted deployments no longer ship shared default credentials; fresh installs generate their own. If yours still uses a previously published default, set a unique value before upgrading, or set
ALLOW_INSECURE_DEFAULT_SECRETS=trueto keep booting while you migrate. - Security
Require explicit browser approval for CLI and MCP login, with resilient polling while approval is pending.
- Security
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. - Security
Prevent prototype pollution when applying run metadata operations or reconstructing nested telemetry attributes, while preserving legitimate
constructorandprototypefields. - Security
Add helpers to mint and verify the deployment-scoped token used to authenticate run controllers to the platform.
- Security
Added optional request rate limiting for telemetry ingestion endpoints.
- Security
Background-worker deployment lookups are now scoped to the authenticated environment.
- Security
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.
Release note
trigger.dev v4.5.6
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.5.6
Release notes
Read the full release notes: trigger.dev/changelog/v4-5-6
Breaking changes
- Breaking
Self-hosted deployments no longer ship shared default credentials; fresh installs generate their own. If yours still uses a previously published default, set a unique value before upgrading, or set
ALLOW_INSECURE_DEFAULT_SECRETS=trueto keep booting while you migrate.
Security patches
- Security
Require explicit browser approval for CLI and MCP login, with resilient polling while approval is pending.
- Security
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. - Security
Prevent prototype pollution when applying run metadata operations or reconstructing nested telemetry attributes, while preserving legitimate
constructorandprototypefields. - Security
Add helpers to mint and verify the deployment-scoped token used to authenticate run controllers to the platform.
- Security
Added optional request rate limiting for telemetry ingestion endpoints.
- Security
Background-worker deployment lookups are now scoped to the authenticated environment.
- Security
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.
- Security
Scope schedule and environment-variable writes to the caller's project and environment
- Security
Reject compute snapshot callbacks that do not match the snapshot request that created them.
- Security
Require secret-key authentication to initialize the session out (agent→client) stream, matching the append route.
- Security
Live run and trace subscriptions now validate their identifiers more strictly and only return data from your own organization.
- Security
Window-function names in the query compiler are now validated against the allowlist, matching how other function calls are handled.
- Security
Authenticate run controllers to the platform with a signed, deployment-scoped token.
- Security
Verify that worker actions (starting, completing, and continuing a run, and reading its snapshots) target a run belonging to the caller's environment.
All packages: v4.5.6
@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.