Atomic deploys

You can now deploy to Trigger.dev without automatically promoting the deploy version to the "current" version, unlocking the ability to deploy atomically between your backend application and your Trigger.dev project.

Usage

You can now deploy with skipping promotion by setting the --skip-promotion flag in the trigger.dev deploy command:

This will deploy your project without promoting the deploy version to the "current" version. You can then promote the deploy version to the "current" version manually using the Trigger.dev dashboard or via the CLI:

TRIGGER_VERSION environment variable

You can now set the TRIGGER_VERSION environment variable in your backend and the @trigger.dev/sdk will automatically use this version when triggering tasks. This allows you to trigger tasks with a specific version of your Trigger.dev project, enabling atomic deploys between your backend and your Trigger.dev project.

See our recently updated deployment overview docs for more about how versions work in Trigger.dev.

Atomic deploys with Vercel

We've tested this new feature to prove that atomic deploys are possible with Vercel, and we've written up an Atomic Deploys guide in our docs to help you get started.

Availability

This feature is available as of version 3.3.17 of the trigger.dev and @trigger.dev/sdk packages. Please reach out to us on our Discord if you have any questions or additional deployment platforms you would like us to provide examples for.