Skip to content

docs: deprecate syncVercelEnvVars extension and add conflict warning #3208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
isshaddad merged 3 commits into from
Mar 11, 2026
+16 −1
Merged

docs: deprecate syncVercelEnvVars extension and add conflict warning #3208

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6a60dda
docs: add deprecation warning to vercel-sync-env-vars guide
isshaddad Mar 11, 2026
b9efde3
docs: warn about syncVercelEnvVars conflict in vercel integration page
isshaddad Mar 11, 2026
2473153
coderabbit changes
isshaddad Mar 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/guides/examples/vercel-sync-env-vars.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,18 @@ description: "This example demonstrates how to sync environment variables from y

import VercelDocsCards from "/snippets/vercel-docs-cards.mdx";

<Warning>
**Deprecated when using the Vercel integration.** If you are using the [Vercel
integration](/vercel-integration), do not use `syncVercelEnvVars` — the integration handles env
var syncing natively and using both together can cause env vars to be incorrectly populated.

If you are **not** using the Vercel integration, `syncVercelEnvVars` is still supported. Continue
with the configuration below.
</Warning>

## Build configuration

To sync environment variables, you just need to add our build extension to your `trigger.config.ts` file. This extension will then automatically run every time you deploy your Trigger.dev project.
If you are not using the [Vercel integration](/vercel-integration), you can sync environment variables manually by adding the `syncVercelEnvVars` build extension to your `trigger.config.ts` file. This extension will run automatically every time you deploy your Trigger.dev project.

<Note>
You need to set the `VERCEL_ACCESS_TOKEN` and `VERCEL_PROJECT_ID` environment variables, or pass
Expand Down
6 changes: 6 additions & 0 deletions docs/vercel-integration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,12 @@ The following variables are excluded from the Vercel → Trigger.dev sync:

You can control sync behavior per-variable from your project's Vercel settings. Deselecting a variable prevents its value from being updated during future syncs.

<Warning>
If you are experiencing incorrectly populated environment variables, check that you are not using
the `syncVercelEnvVars` build extension in your `trigger.config.ts`. This extension is deprecated
and conflicts with the Vercel integration's built-in env var syncing. Remove it if present.
</Warning>

### Supabase and Neon database branching

If you use [Supabase Branching](https://supabase.com/docs/guides/deployment/branching) or [Neon Database Branching](https://neon.tech/docs/guides/branching-intro) for preview environments, disable syncing for database env vars on the Environment Variables page and use the [syncSupabaseEnvVars](/config/extensions/syncEnvVars#syncsupabaseenvvars) or [syncNeonEnvVars](/config/extensions/syncEnvVars#syncneonenvvars) build extensions instead. These extensions automatically resolve the correct branch-specific credentials at build time.
Expand Down
Loading