Packages

@trigger.dev/sdk

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

Upgrading @trigger.dev/sdk From 4.6.4 to 4.7.0

1 release in betweenevery note read

Other targets from 4.6.4Newest 4.x, Latest4.8.8
  1. 4.6.4yours
  2. 4.7.0target

Before you upgrade

Tick each one off as you go
  • Deprecated4.7.0
  • Deprecated4.7.0

Release by release

  1. 4.7.0

    Deprecation1 Oct 202614 new · 6 fixes
    • Deprecated

      The queue-level concurrencyLimit option keeps working unchanged and is deprecated in favor of concurrency.

    • Deprecated

      Deprecate queues.overrideConcurrencyLimit and queues.resetConcurrencyLimit. These operate on the legacy model where a queue carried its own concurrency limit; declare concurrency with the task concurrency option and manage it with concurrencyLimits.override and concurrencyLimits.reset instead.

    • New

      Chat agents can now scope concurrency per session. Pass concurrencyKey (for example, your chat ID or tenant ID) and trigger-time named limits via triggerConfig.concurrency when starting a chat session, from chat.createStartSessionAction, the AgentChat client, or a handover. Keys are never defaulted, so a session without one shares the task's keyless pool.

    • New

      Concurrency limits can now be paused and resumed, just like queues: concurrencyLimits.pause(name) stops every run holding the limit from being dequeued while keeping its configured bounds, and concurrencyLimits.resume(name) starts them again.

15 other lines we could not sort, mostly version bumps
  • One concurrency key with a large backlog no longer holds up runs waiting on other keys on the same queue.

    4.7.0
  • API rate limit usage is now recorded per environment in the metrics table as api.rate_limit.allowed, api.rate_limit.denied, api.rate_limit.remaining_min and the limit itself (api.rate_limit.limit.per_second and api.rate_limit.limit.burst), so you can chart requests against your limit and 429s over time on the Query page and dashboards.

    4.7.0
  • Archive queues you no longer use from the Concurrency page. Archived queues are hidden from the list and no longer count towards allocated concurrency.

    4.7.0
  • Automatically archive preview branches after a configurable period without deployments, with protected branch names and a preview of affected branches.

    4.7.0
  • Download a session’s original saved transcript file from the session inspector.

    4.7.0
  • Organization Owners and Admins can now choose, in Settings under Support Access, whether Trigger.dev support can open their dashboard directly or only after an Owner or Admin approves a request, with each approval lasting 7 days.

    4.7.0
  • Allocating extra concurrency to environments now requires billing permissions, the same as purchasing it. Allocation changes are also applied atomically, so simultaneous edits can no longer exceed your purchased concurrency.

    4.7.0
  • Changing your account email address now sends a confirmation link to the new address; the change only takes effect once that link is opened. Requesting a magic link no longer creates an account until the link is used.

    4.7.0
  • Removed the organization-wide Node.js 21 deprecation banner while keeping runtime upgrade guidance in Projects settings.

    4.7.0
  • Creating a project now asks only for its name.

    4.7.0

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.