@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
180 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 2.x
2.0.5
8 Aug 2023Reading the note…
2.0.4
7 Aug 2023Reading the note…
2.0.3
3 Aug 2023Reading the note…
2.0.2
2 Aug 2023Reading the note…
2.0.1
2 Aug 2023Reading the note…
2.0.0
2 Aug 2023- Deprecated
Deprecated the
JobOptions.queueoptions as we are no longer using that to control job concurrency. We'll add proper queue support in the future. Fixed the cached task miss issue in the
@trigger.dev/sdkwhich should speed up resumed runs by A LOTAllow setting graphile worker concurrency settings through env vars
WORKER_CONCURRENCYandEXECUTION_WORKER_CONCURRENCY
Trigger.dev v2.0.0
We've dropped the
betalabel on our v2.0.0 release of the Trigger.dev service, and moving forward we'll be updating the version number like good semantic version citizens.The following changes have been made in the last few weeks:
Increased performance
We've redesigned the way we queue and execute job runs in order to increase the speed of job execution.
Fixed the cached task miss issue in the
@trigger.dev/sdkwhich should speed up resumed runs by A LOTAllow setting graphile worker concurrency settings through env vars
WORKER_CONCURRENCYandEXECUTION_WORKER_CONCURRENCYAllow settings prisma pool settings through env vars
DATABASE_CONNECTION_LIMITandDATABASE_POOL_TIMEOUTYou can now selectively enable/disable the workers through
WORKER_ENABLED=falseandEXECUTION_WORKER_ENABLED=false. This means the image can be deployed as 2 or 3 separate services:A WebApp service that serves the API and the Dashboard
A Worker service that runs tasks that have been added the standard worker
An Execution Worker service that only runs "run execution" tasks
- Deprecated
Deprecated the
JobOptions.queueoptions as we are no longer using that to control job concurrency. We'll add proper queue support in the future.
Fixed runs with large task outputs
We had an issue where runs that included tasks that had large task outputs could not be resumed after a delay.
This was because we send completed task outputs in the request body when we resume a run, and some platforms have a limit on the size of the request body.
We now cap the size of the task outputs we send in the request body to 3.5MB.Disable and delete jobs
You can now disable jobs in your code by setting the
enabledoption tofalse:client.defineJob({ id: "example-job", name: "Example Job", version: "0.1.0", trigger: eventTrigger({ name: "example.event" }), enabled: false, run: async (payload, io, ctx) => { // your job code here }, });Which will show the job as disabled in the dashboard:
CleanShot 2023-08-23 at 16 27 33
Once you've disabled your job, you can delete it from the dashboard:
CleanShot 2023-08-23 at 16 34 36
For more detailed information, checkout our documentation on managing jobs.
Cancel delayed events
When sending events, you can delay the delivery by setting either the
deliverAtordeliverAfteroption:await client.sendEvent( { id: "event-1", name: "example.event", payload: { hello: "world" }, }, { deliverAfter: 1000 * 60 * 60 * 24, // 1 day } );You can now easily cancel delayed events to prevent subsequent job runs with the new
cancelEventmethod:await client.cancelEvent("event-1");This functionality requires
@trigger.dev/sdk@2.0.11or later.@trigger.dev/openai v2.0.11
We've updated our OpenAI package to use the new and improved v4 of the OpenAI SDK.
All of our existing tasks should work as before, but now when you use the
.nativeproperty you'll get back and nice and shiny v4 SDK:import { OpenAI } from "@trigger.dev/openai"; const openai = new OpenAI({ id: "openai", apiKey: process.env["OPENAI_API_KEY"]!, }); // Before: v3 SDK openai.native.createCompletion({...}); // Now: v4 SDK openai.native.completions.create({...});We've also added some new tasks for enabling fine tuning jobs:
createFineTuningJob- Create a fine-tuning job for a fine-tuning modelretrieveFineTuningJob- Retrieve a fine-tuning job for a fine-tuning modellistFineTuningJobs- List fine-tuning jobs for a fine-tuning modelcancelFineTuningJob- Cancel a fine-tuning job for a fine-tuning modellistFineTuningJobEvents- List fine-tuning job events for a fine-tuning model
@trigger.dev/cli v2.0.11
Our CLI has been updated with some fixes and improvements:
3ce5397: Added the send-event command
3897e6e: Make it more clear which API key the init command expects
dd10717: Added
--hostnameoption to the cli dev command8cf8544: Bugfix: @trigger.dev/cli init now correctly identifies the App Dir when using JS (thx @Chigala ✨)
4e78da3: fix: Add an update sub-command the @trigger.dev/cli that updates all @trigger.dev/* packages (thx @hugomn ✨)
135cb49: fixed the cli init log message to show the correct path to the app route created (thx @Chigala ✨)
@trigger.dev/react v2.0.11
New package: @trigger.dev/astro
Thanks to Liran Tal, we now have a native package to use Trigger.dev with Astro.
This is just the beginning and you can keep track of our progress on bringing Trigger.dev to Astro here
How to update
To update your existing projects to the latest version of the SDK, run the following command:
npx @trigger.dev/cli update
If you are self-hosting the Trigger.dev service, you'll need to update to the
latestimage:docker pull triggerdotdev/trigger.dev:v2.0.0 # or docker pull triggerdotdev/trigger.dev:latest@sha256:00d9d9646c3781c04b84b4a7fe2c3b9ffa79e22559ca70ffa1ca1e9ce570a799
If you are using the Trigger.dev Cloud, you'll automatically get the latest version of the service.
Upcoming changes
We're working on some exciting new features for upcoming releases:
Matt is working on our
@trigger.dev/airtableintegration, which will allow you to interact with Airtable from your jobs and trigger jobs on changes that occur in your Airtable bases. This one is taking a bit longer than expected on account of some interesting challenges and limitations in the Airtable Webhook implementation, but we're getting close.Dan is working on a new Job Showcase repo and page on our public site to show off some example use-cases for Trigger.dev. We're hoping this will help people get started with Trigger.dev and give some ideas on how to use it in your own projects.
James is working on more dashboard improvements, which he'll be sharing on our Twitter/X soon.
Eric is working on a feature called Background Tasks, which will allow you to create specific tasks that can execute for up to 1 hour without pause. This will be useful for doing tasks that take longer than a serverless function timeout, like training ML models, or doing large data processing tasks.
As always, if you have any questions or feedback, please reach out to us on Twitter/X or Discord.
- 0.2.x
0.2.22
15 Mar 2023Reading the note…
0.2.21
2 Mar 2023Reading the note…
0.2.20
2 Mar 2023Reading the note…
0.2.19
27 Feb 2023Reading the note…
0.2.18
27 Feb 2023Reading the note…
0.2.17
27 Feb 2023Reading the note…
0.2.15
21 Feb 2023Reading the note…
0.2.14
16 Feb 2023Reading the note…
0.2.13
7 Feb 2023Reading the note…
0.2.12
6 Feb 2023Reading the note…
0.2.11
28 Jan 2023Reading the note…
0.2.10
26 Jan 2023Reading the note…
0.2.9
26 Jan 2023Reading the note…
0.2.8
25 Jan 2023Reading the note…
0.2.7
24 Jan 2023Reading the note…
0.2.6
23 Jan 2023Reading the note…
0.2.5
21 Jan 2023Reading the note…
0.2.4
20 Jan 2023Reading the note…
0.2.3
20 Jan 2023Reading the note…
0.2.2
20 Jan 2023Reading the note…
0.2.1
16 Jan 2023Reading the note…
0.2.0
15 Jan 2023Reading the note…
- 0.1.x
0.1.2
15 Jan 2023Reading the note…
0.1.1
13 Jan 2023Reading the note…
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.