Skip to content

docs: document secret env vars and Vercel sync behavior #3419

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
Apr 20, 2026
+15 −0
Merged

docs: document secret env vars and Vercel sync behavior #3419

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
b74e01e
docs: clarify Vercel env var sync requires a new deployment
isshaddad Apr 20, 2026
09ca544
docs: document secret environment variables
isshaddad Apr 20, 2026
fdf48f6
Merge branch 'main' into docs/env-var-secrets-and-vercel-sync
isshaddad Apr 20, 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
9 changes: 9 additions & 0 deletions docs/deploy-environment-variables.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,15 @@ We deploy your tasks and scale them up and down when they are triggered. So any
locally.
</Note>

### Secret environment variables

When creating an environment variable, you can mark it as a **Secret**. Secret values are hidden in the dashboard and cannot be viewed after creation.

<Warning>
Marking a variable as a Secret is irreversible and can only be done when creating the variable. To
change this setting, you must delete the variable and create a new one.
</Warning>

### Editing environment variables

You can edit an environment variable's values. You cannot edit the key name, you must delete and create a new one.
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.

<Note>
Environment variables are pulled from Vercel before each build. To sync updated values into
Trigger.dev, trigger a new Vercel deployment — either by pushing a commit to your connected branch
or by redeploying from the Vercel dashboard.
</Note>

<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
Expand Down
Loading