From c9c2773f119e32ad6ae53051ac08f1baf371447e Mon Sep 17 00:00:00 2001 From: Goutam0612 Date: Thu, 25 Jun 2026 01:54:49 +0530 Subject: [PATCH] fix: let Vercel build remotely instead of building in Gitea runner Co-Authored-By: Claude Opus 4.8 (1M context) --- .gitea/workflows/deploy.yml | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 5d5f307..2f52c30 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -1,6 +1,7 @@ name: Deploy to Vercel -# Jab bhi 'revamp' branch pe push hoga, yeh automatically Vercel pe deploy kar dega +# Jab bhi 'revamp' branch pe push hoga, yeh automatically Vercel pe deploy kar dega. +# Build Vercel ke servers pe hota hai (runner sirf code upload karta hai) — fast & reliable. on: push: branches: @@ -23,17 +24,8 @@ jobs: with: node-version: "22" - - name: Enable pnpm - run: corepack enable - - name: Install Vercel CLI run: npm install -g vercel@latest - - name: Pull Vercel project settings - run: vercel pull --yes --environment=production --token="$VERCEL_TOKEN" - - - name: Build project - run: vercel build --prod --token="$VERCEL_TOKEN" - - - name: Deploy to production - run: vercel deploy --prebuilt --prod --token="$VERCEL_TOKEN" + - name: Deploy to production (Vercel builds remotely) + run: vercel deploy --prod --yes --token="$VERCEL_TOKEN"