@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 3.0.0 to 3.3.17
37 releases in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 9
- new
- 18
- fixes
Before you upgrade
Tick each one off as you go- Breaking3.1.1
Release by release
- New
Add support for two-phase deployments and task version pinning
- New
- Fixed
You can add Alerts in the dashboard. One of these is a webhook, which this change greatly improves.
- Fixed
- Fixed
Detect ffmpeg OOM errors, added manual OutOfMemoryError
- Fixed
- New
Added the ability to retry runs that fail with an Out Of Memory (OOM) error on a larger machine.
- New
- Fixed
Fixed issue with asResponse and withResponse not working on runs.retrieve
- Fixed
3.3.12nothing new or fixed in the note
- New
Add support for specifying machine preset at trigger time. Works with any trigger function:
- New
3.3.10nothing new or fixed in the note
4 other lines we could not sort, mostly version bumps
- 3.3.0
The new Batch Trigger endpoint is now asynchronous and supports up to 500 runs per request.
- 3.3.0
The new endpoint also supports triggering multiple different tasks in a single batch request (support in the SDK coming soon).
- 3.3.0
The existing
batchTriggermethod now supports the new endpoint, and shouldn't require any changes to your code. - 3.3.0
Idempotency keys now expire after 24 hours, and you can customize the expiration time when creating a new key by using the
idempotencyKeyTTLparameter:
37 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.