From fd4c3cc1aa1b822bf054203e9943d603933fe666 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=EC=9D=B4=EC=9D=80=EC=84=9D?= Date: Sat, 28 Feb 2026 11:56:16 +0900 Subject: [PATCH] fix(ci): use --build-env for NEXT_PUBLIC vars in Vercel deploy NEXT_PUBLIC_* vars must be available at build time for Next.js. Changed from -e (runtime) to --build-env (build time). Co-Authored-By: Claude Opus 4.6 --- .github/workflows/ci-cd.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci-cd.yml b/.github/workflows/ci-cd.yml index aec317f..6dd3b56 100644 --- a/.github/workflows/ci-cd.yml +++ b/.github/workflows/ci-cd.yml @@ -89,7 +89,7 @@ jobs: max_attempts=3 while :; do if vercel deploy --confirm --token "$VERCEL_TOKEN" --scope "$VERCEL_SCOPE" \ - -e NEXT_PUBLIC_API_BASE="${{ secrets.NEXT_PUBLIC_API_BASE_DEV }}"; then + --build-env NEXT_PUBLIC_API_BASE="${{ secrets.NEXT_PUBLIC_API_BASE_DEV }}"; then break fi @@ -149,7 +149,7 @@ jobs: max_attempts=3 while :; do if vercel deploy --prod --confirm --token "$VERCEL_TOKEN" --scope "$VERCEL_SCOPE" \ - -e NEXT_PUBLIC_API_BASE="${{ secrets.NEXT_PUBLIC_API_BASE_PROD }}"; then + --build-env NEXT_PUBLIC_API_BASE="${{ secrets.NEXT_PUBLIC_API_BASE_PROD }}"; then break fi