Vercel Deployment

Workflow

Phase 1: Pre-flight Checks

1. Verify Vercel CLI is installed (

   vercel --version

   ). If not:

   npm i -g vercel

2. Verify authentication:

   vercel whoami

   . If not logged in:

   vercel login

3. Determine project name from the current working directory folder name using

   basename "$(pwd)"

Phase 2: Deploy

--yes

vercel --yes

vercel --yes --prod

--yes

Phase 3: Disable Vercel Authentication

Option A: Using the deploy script (preferred)

# Set token for API access
export VERCEL_TOKEN="<token>"
# Optional: set team ID if using a team
export VERCEL_TEAM_ID="<team-id>"

# Preview deploy
bash scripts/deploy.sh /path/to/project

# Production deploy
bash scripts/deploy.sh /path/to/project prod

Option B: Manual API call after deploying

ssoProtection

PROJECT_NAME=$(basename "$(pwd)")

curl -X PATCH "https://api.vercel.com/v9/projects/$PROJECT_NAME" \
  -H "Authorization: Bearer $VERCEL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"ssoProtection": null}'

?teamId=<TEAM_ID>

Option C: Using Vercel CLI curl

vercel curl -X PATCH "/v9/projects/$(basename "$(pwd)")" \
  -H "Content-Type: application/json" \
  -d '{"ssoProtection": null}'

Phase 4: Verify

1. Confirm deployment URL is accessible without Vercel login
2. Print the deployment URL for the user

Environment Variables

VERCEL_TOKEN

VERCEL_TEAM_ID

Notes

• The

  --yes

  flag uses the folder name as the project name by default
• If

  VERCEL_TOKEN

  is not set, deployment still works but Vercel Authentication won't be auto-disabled. Inform the user they can disable it manually in: Vercel Dashboard > Project > Settings > Deployment Protection > Vercel Authentication > Off
• Setting

  ssoProtection

  to

  null

  disables Vercel Authentication for all deployments (preview and production)