vercel@51.8.0
Breaking Changes📦 vercel-cliView on GitHub →
⚠ 1 breaking✨ 2 features🐛 2 fixes🔧 1 symbols
Summary
The Vercel CLI now defaults environment variables to sensitive for Production and Preview deployments, introducing new flags and stricter handling for Development targets. Numerous internal Vercel builder dependencies were also updated.
⚠️ Breaking Changes
- When using `vercel env add` interactively or with a mixed selection of targets that includes Development, the command now errors because Development environments cannot share a record type (encrypted) with Production/Preview (now defaulting to sensitive). You must run `vercel env add` separately for Development.
Migration Steps
- If you rely on environment variables being readable via the dashboard/CLI for Production or Preview targets, use the new `--no-sensitive` flag when running `vercel env add`.
- If you previously used `vercel env add` with Development and other targets simultaneously, you must now run `vercel env add` separately for the Development target.
✨ New Features
- `vercel env add` now defaults Environment Variables to sensitive on Production and Preview targets.
- Introduced the `--no-sensitive` flag to opt out of the new sensitive default for Production/Preview environments.
🐛 Bug Fixes
- Passing `--sensitive` alongside a Development target now errors up-front instead of silently falling back to encrypted.
- On teams with the "Enforce Sensitive Environment Variables" policy active, the CLI now correctly emits a warning when `--no-sensitive` is used for Production/Preview variables, as the server enforces sensitive storage regardless.