| name | env-update |
| description | Use when adding, removing, or renaming environment variables in the project. Ensures turbo.json stays in sync and naming conventions are followed. |
Environment Variables
Rules
-
turbo.json must stay in sync. Every env var used by any app must be declared in turbo.json under tasks.build.env. Turborepo uses this list to track build cache invalidation and Vercel will warn about missing entries.
-
NEXT_PUBLIC_ prefix means the variable is inlined into the client bundle at build time and visible to anyone. Only use it for values that are safe to expose publicly (e.g. brand slug, Sentry DSN, Turnstile site key). Never use it for API keys, secrets, or tokens. Do NOT add NEXT_PUBLIC_* vars to Vercel project settings - they are public, so they belong in each app's ``.env.production` in each app, not in Vercel's secret store.
-
Server-only variables (no NEXT_PUBLIC_ prefix) are only available in server components, server actions, route handlers, and next.config.ts. Use this for all secrets (API_URL, BREVO_API_KEY, PACMS_API_KEY, TURNSTILE_SECRET_KEY, SENTRY_AUTH_TOKEN). These must be set in Vercel project settings.
Checklist when adding a new env var
Checklist when removing an env var
Current turbo.json env list
Keep this alphabetically sorted:
API_URL, BREVO_API_KEY, NEXT_PUBLIC_SENTRY_DSN, PACMS_API_KEY, SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT, TURNSTILE_SECRET_KEY
