chore: stage/prod 배포 및 승격 워크플로우를 web/admin 분리 운영으로 정비

[manNomi]

Summary

• main push 시 stage 배포가 동작하도록 web/admin 공통 deploy-stage.yml을 추가하고, shared package(packages/**) 변경도 배포 트리거에 포함했습니다.
• production 배포는 release 승격형으로 전환하고, release.yml에서 target(web/admin/both) 입력으로 release-web/release-admin 브랜치를 선택 승격하도록 분리했습니다.
• Vercel 프로젝트 시크릿 참조를 2개 프로젝트 체계(VERCEL_PROJECT_ID_WEB, VERCEL_PROJECT_ID_ADMIN)로 단순화하고, turbo outputs에 .vercel/output/**를 포함해 캐시 복원 안정성을 높였습니다.

Required Settings

• Vercel web project Production Branch: release-web
• Vercel admin project Production Branch: release-admin
• GitHub Actions secrets:
  • VERCEL_TOKEN
  • VERCEL_ORG_ID
  • VERCEL_PROJECT_ID_WEB
  • VERCEL_PROJECT_ID_ADMIN
  • TURBO_TOKEN
  • TURBO_TEAM

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
solid-connect-web-admin	Ready	Preview, Comment	Feb 16, 2026 10:46am
solid-connection-web	Ready	Preview, Comment	Feb 16, 2026 10:46am

[coderabbitai]

Warning

Rate limit exceeded

@manNomi has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minutes and 54 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

세 가지 주요 변경사항이 추가되었습니다.

1. .github/workflows/deploy-stage.yml 신규 추가

   • GitHub Actions 워크플로우로, 변경 경로를 탐지하여 web, admin, shared, root 그룹으로 분류합니다.
   • 두 개의 배포 작업(deploy-web-stage, deploy-admin-stage)을 조건부로 실행하며, 각각은 체크아웃, 의존성 설치, 빌드, Vercel 배포 등의 단계를 수행합니다.

2. .github/workflows/release.yml 수정

   • 워크플로우 이름을 변경하고 promotion 대상 입력값을 추가합니다.
   • 기존 배포 단계를 제거하고 main 브랜치를 release 브랜치로 승격하는 git 기반 작업으로 교체합니다.

3. turbo.json 수정

   • 빌드 작업의 출력 배열에 .vercel/output/**을 추가합니다.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Suggested reviewers

• wibaek
• enunsnv
• khwww

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Merge Conflict Detection	⚠️ Warning	❌ Merge conflicts detected (2 files): ⚔️ .github/workflows/deploy-stage.yml (content) ⚔️ .github/workflows/release.yml (content) These conflicts must be resolved before merging into main.	Resolve conflicts locally and push changes to this branch.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	PR 제목이 web/admin 분리 운영으로의 배포 워크플로우 정비라는 주요 변경사항을 명확하게 요약하고 있습니다.
Description check	✅ Passed	PR 설명이 변경사항 요약과 필수 설정을 포함하고 있으나, 리포지토리의 한국어 템플릿과 비교하면 '관련 이슈', '특이 사항', '리뷰 요구사항' 섹션이 누락되어 있습니다.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/unify-stage-prod-vercel-deploy

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}