Use atomic deploys to coordinate changes to your tasks and your application.
--skip-promotion
flag. This creates a new task version without making it the default.TRIGGER_VERSION
to the captured task version.npx trigger.dev deploy
command uses --skip-promotion
to deploy the tasks without setting the version as the default.deploy-trigger
allows us to capture the deployment version in the output (deploymentVersion).npx vercel
command deploys the application, setting the TRIGGER_VERSION
environment variable to the task version from the previous step.@trigger.dev/sdk
automatically uses the TRIGGER_VERSION
environment variable to trigger the correct version of the tasks.TRIGGER_ACCESS_TOKEN
: Your Trigger.dev personal access token. View the instructions here to learn more.VERCEL_TOKEN
: Your Vercel personal access token. You can find this in your Vercel account settings.https://vercel.com/<team-slug>/<project-slug>/settings/environments/production
ludalex/vercel-wait
action.npx trigger.dev deploy
command. There’s no need to use the --skip-promotion
flag because we want to promote the deployment.npx vercel promote
command.TRIGGER_ACCESS_TOKEN
: Your Trigger.dev personal access token. View the instructions here to learn more.VERCEL_TOKEN
: Your Vercel personal access token. You can find this in your Vercel account settings.VERCEL_PROJECT_ID
: Your Vercel project ID. You can find this in your Vercel project settings.VERCEL_SCOPE_NAME
: Your Vercel team slug.ludalex/vercel-wait
action above as a fork of the official
tj-actions/vercel-wait action because there is a bug
in the official action that exits early if the deployment isn’t found in the first check and due
to the fact that it supports treating skipped (cancelled) Vercel deployments as valid (on by default).
I’ve opened a PR for this issue here.