ELSEIF
Your brief EB
449 stories from 200 feeds 1255 clusters Refreshed 19 minutes ago next pull 21:12

WEB Signal 88

Environment variables now use Config and Secret types

Vercel now requires choosing Config or Secret for environment variables instead of using a Sensitive toggle, with existing Sensitive variables automatically treated as Secrets.

WHY IT MATTERS

Engineers managing Vercel deployments get clearer control over which variable values remain readable after saving. The new types also come with a deprecated team policy and a new optional policy for separating production secret values, so teams must review their security settings.

Written by elseif from the cluster below · every claim links back to a source

The three things worth knowing

01

Config variables stay readable after saving, while Secret variables cannot be viewed or retrieved by members.

02

Existing variables marked Sensitive are automatically treated as Secrets and require no migration.

03

The Enforce Sensitive Environment Variables team policy is deprecated, and a new Separate Production Secret Values policy is available in Security settings.

THE CLUSTER

Same story, 1 feed.

ORDERED BY FIRST SEEN
Vercel Environment variables now use Config and Secret types Open ↗