Vercel replaces Sensitive toggle with Config and Secret environment variable types

What shipped? Vercel replaced the binary Sensitive toggle on environment variables with two explicit types: Config and Secret.

What changed? When you add or edit an environment variable in the dashboard, you now choose either Config (value readable after saving by team members with access) or Secret (value locked after saving — members cannot view or retrieve it). Existing variables marked Sensitive were auto-migrated to Secrets — no migration needed. The "Enforce Sensitive Environment Variables" team policy is deprecated; teams can now pick the right type per variable instead of forcing everything to Sensitive.

Why does a builder care? If you've ever had to rotate an API key because a teammate accidentally read it in the dashboard, or been blocked from inspecting a misconfigured public prefix variable that was locked down as Sensitive — this fix is for you. Config and Secret map cleanly to the actual sensitivity of the value, and the deprecation of the blanket enforcement policy means teams can stop treating non-sensitive config like a password.