Packages

@trigger.dev/sdk

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

Upgrading @trigger.dev/sdk From 2.0.0 to 2.3.19

55 releases in betweennotes for 3

Other targets from 2.0.0Latest4.8.8
  1. 2.0.0yours
  2. 24 releases
  3. 2.2.0breaking
  4. 29 releases
  5. 2.3.19target
1+
change to make
0
advisories fixed
1+
new
?
fixes

Counted from 3 of 55 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking2.2.0

Release by release

  1. 2.3.1 – 2.3.1918 releases, no release note

  2. 2.3.0

    6 Dec 20231 new
    • New

      Support for Deno, Bun and Cloudflare workers, as well as conditionally exporting ESM versions of the package instead of just commonjs.

  3. 2.2.1 – 2.2.1111 releases, no release note

  4. 2.2.0

    Migration needed13 Oct 2023
    • Breaking

      Drop support for Node v16, require Node >= 18. This allows us to use native fetch in our SDK which paves the way for multi-platform support.

  5. 2.0.1 – 2.1.924 releases, nothing new or fixed; 23 without a note

24 other lines we could not sort, mostly version bumps
  • Gets all the records (rows)

    2.1.0
  • Gets a single record

    2.1.0
  • Create a new record

    2.1.0
  • Updates the record that was just created

    2.1.0
  • Waits 5 seconds

    2.1.0
  • Deletes the record that was created/updated

    2.1.0
  • @trigger.dev/airtable

    2.1.0
  • @trigger.dev/sdk

    2.1.0
  • @trigger.dev/github

    2.1.0
  • @trigger.dev/openai

    2.1.0

2 internal lines (docs, tests, tooling) left out.

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.