vercel-ops

Operate an existing Vercel project without leaking values, targeting the wrong project or environment, or mistaking an environment change for a deployed change.

When to Use

• Audit, add, update, or synchronize Vercel environment variables
• Diagnose trailing whitespace or cross-provider value mismatches without printing values
• Verify a NEXT_PUBLIC_* value was compiled into a new deployment
• Inspect deployment protection or smoke-test a protected deployment
• Attach or verify a custom domain without assuming a DNS-provider change
• Create an explicit, on-demand Preview deployment

When Not to Use

• Production deployment execution; use vercel-deploy
• Creating a Vercel project or connecting a Git repository
• Enabling automatic Preview deployments for every branch
• Editing DNS at an external provider without that provider's runbook and explicit authorization