Packages

@trigger.dev/sdk

4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed

Upgrading @trigger.dev/sdk From 4.8.2 to 4.8.3

1 release in betweenevery note read

Other targets from 4.8.2Newest 4.x, Latest4.8.8
  1. 4.8.2yours
  2. 4.8.3target
1
change to make
0
advisories fixed
4
new
3
fixes

Before you upgrade

Tick each one off as you go
  • Deprecated4.8.3

Release by release

  1. 4.8.3

    Deprecation30 Oct 20264 new · 3 fixes
    • Deprecated

      Deprecates the legacy Bun runtime. runtime: "bun" (and its explicit spelling "bun-legacy"), which deploys Bun 1.3.3 with Node.js 20 alongside it, now prints a deprecation warning, and deploys that use it will be rejected from January 5, 2027. Switch to runtime: "bun-1.4" (Bun 1.4.4 on an image with no Node.js binary) and redeploy.

    • New

      CLI and MCP logins are now bound to the machine that started them. Approving a login in your browser sends you back to the CLI automatically, or, when the browser is on another machine, shows a code to paste into the terminal (or pass with trigger.dev login --code). Older CLI versions will need to upgrade to log in.

    • New

      Add trigger webhooks set-secret and trigger webhooks generate-secret, which store a webhook endpoint's signing secret without printing it. set-secret reads the secret from a pipe, an environment variable or a .env file, and generate-secret saves the new secret to an env file. When the endpoint already has a secret, both ask how long the old one keeps working (or take --previous-secret-ttl 24h in scripts). The MCP server's set_webhook_secret and generate_webhook_secret descriptions now point AI agents at these commands, so the secret stays out of the agent's context.

    • New

      Add trigger.refresh(ctx, id) to request an earlier status check for a Convex-tracked run, so applications using Trigger Realtime can publish results without waiting for the next scheduled poll. Requests are coalesced and rate-limited, use the existing completion callback, and retain polling as a recovery fallback.

4 other lines we could not sort, mostly version bumps
  • The CLI and MCP login consent page now shows when and from which IP address the login was started, and you get an email whenever a new CLI or MCP login is authorized on your account.

    4.8.3
  • Searching, filtering to errors, and expanding or collapsing spans in the run trace view are faster on large traces.

    4.8.3
  • Guide switching from shared root keys to individually managed API keys, while keeping root key regeneration directly available.

    4.8.3
  • CLI and MCP login codes now work once, and every login mints its own personal access token instead of reusing an existing CLI token.

    4.8.3

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.