🔥 릴리즈 승격 워크플로에서 admin 타깃 제거 (admin: main 병합 = 프로덕션 배포)

[manNomi]

요약

• Promote Main to Release Branches workflow에서 admin 타깃만 제거합니다. web/university의 release branch 승격 배포는 그대로 유지됩니다.
• admin은 이제 main 병합만으로 프로덕션이 배포되는 모델로 전환합니다. release-admin 승격 단계가 사라집니다.
• docs/git-cicd.md, docs/university-multizone-deployment.md의 admin 배포 설명을 갱신했습니다.

배경

어드민에 API 환경(stage/prod) 런타임 전환이 도입되면서(#615, #616, 후속으로 플로팅 스위처 예정) 어드민을 stage + production 이중으로 관리할 필요가 없어졌습니다. admin 배포를 main 하나로 통합하고, stage/prod API 전환은 앱 안에서 처리합니다.

필요한 후속 작업 (Vercel, 저장소 설정)

• Vercel Admin Project의 Production Branch를 release-admin → main으로 변경 (@hanmw110 진행 예정)
• 전환 확인 후 원격의 release-admin 브랜치 정리(선택)

특이 사항

• 이 PR 머지 후 Vercel Admin Project의 production branch를 바꾸기 전까지는 release-admin이 더 이상 갱신되지 않으므로 admin 프로덕션 배포 수단이 일시적으로 없습니다. 머지 직후 Vercel 설정 변경을 권장합니다.
• admin의 HeadVer 태깅/GitHub Release 생성은 승격 workflow 안에 있었으므로 이 PR 이후 admin 자동 태깅이 중단됩니다(web/university 태깅은 유지). .github/scripts/create-headver-tag.sh의 admin 분기는 다른 곳에서 재사용될 수 있어 남겨두었습니다.
• web, university-web의 배포 흐름은 변경하지 않았습니다.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
solid-connect-university-web	Ready	Preview	Aug 1, 2026 4:25pm
solid-connect-web-admin	Ready	Preview	Aug 1, 2026 4:25pm
solid-connection-web	Ready	Preview	Aug 1, 2026 4:25pm

[coderabbitai]

Walkthrough

1. 프로덕션 배포 경로 변경
   main 브랜치 push가 각 Vercel Project의 production 배포를 직접 트리거하도록 문서를 갱신했습니다. 릴리스 브랜치 승격 절차와 관련 workflow 설명을 제거했습니다. .github/workflows/release.yml을 삭제했습니다.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: wibaek, enunsnv, khwww

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	제목은 admin 릴리스 대상 제거를 설명하며 변경사항과 관련되지만, 전체 릴리스 워크플로 제거를 명시하지 않습니다.
Description check	✅ Passed	설명은 변경 내용, 배경, 후속 작업, 배포 중단 위험을 포함해 대부분의 필수 정보를 제공합니다.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/remove-prod-release-cd

---

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.}

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/git-cicd.md`:
- Around line 42-44: Update the versioning section in docs/git-cicd.md to
separate headver.json’s app-specific head values from HEADVer tag creation
performed by .github/workflows/headver-tagging.yml. Clarify that post-deployment
manual updates and Promote Main to Release Branches/release-* branch promotion
are not part of the current process, rather than documenting them as required
operational steps.

In `@docs/university-multizone-deployment.md`:
- Around line 69-75: The deployment documentation must explicitly require
updating Vercel settings before relying on main-branch production deployments.
In docs/university-multizone-deployment.md lines 69-75, add steps before the
production-branch guidance to set each Vercel Project’s Settings > Git >
Production Branch to main. In docs/git-cicd.md lines 42-44, state that this
Vercel configuration must be completed before describing main pushes as
triggering production deployments.
- Around line 69-75: 문서의 Vercel production 배포 설명에 각 프로젝트의 설정 절차를 추가하세요. Main
Web, Admin, University Web Project에서 각각 Settings > Git의 Production Branch를
main으로 지정하고, 설정 전환 후 main push가 production 배포를 트리거하는지 확인하는 단계까지 명시하세요.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b52f431e-83cc-49eb-ac75-bd764c1b61d0

📥 Commits

Reviewing files that changed from the base of the PR and between 97f1cb0 and 65ffeff.

📒 Files selected for processing (3)

• .github/workflows/release.yml
• docs/git-cicd.md
• docs/university-multizone-deployment.md

💤 Files with no reviewable changes (1)

• .github/workflows/release.yml

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== files =="
git ls-files | sed -n '1,120p'

echo "== docs/git-cicd.md lines 1-90 =="
cat -n docs/git-cicd.md | sed -n '1,90p'

echo "== workflow/headver/release references =="
rg -n "HeadVer|headver|release branch|release-web|release-admin|release-university|GitHub Release|Promote Main|create.*release|Create Release|gh release|release" -S . --glob '!node_modules' --glob '!dist' --glob '!build' | sed -n '1,240p'

Repository: solid-connection/solid-connect-web

Length of output: 8249

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow files =="
cat -n .github/workflows/ci.yml
echo "---"
cat -n .github/workflows/headver-tagging.yml

echo "== scripts =="
cat -n .github/scripts/create-headver-tag.sh

echo "== headver.json tracked/config =="
for f in $(git ls-files | grep -E '(^|/)headver\.json$|^pnpm-workspace\.yaml$|^package\.json$'); do
  echo "--- $f"
  sed -n '1,120p' "$f"
done

echo "== docs onboarding lines 45-58 =="
cat -n docs/onboarding.md | sed -n '45,58p'

Repository: solid-connection/solid-connect-web

Length of output: 14206

---

1. HeadVer 태깅과 release branch 과정을 문서에서 분리하세요.

docs/git-cicd.md의 버저닝 섹션이 현재 CI 상태와 맞지 않습니다. headver.json은 현재 앱별 head 값만 저장되고, HEADVer 태깅은 .github/workflows/headver-tagging.yml에서 별도 호출해 생성합니다. 배포 이후 수동 업데이트나 Promote Main to Release Branches/release-* branch 갱신 과정을 운영 절차에 추가하거나, 현재 절차가 아님을 분명히 적어주세요.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/git-cicd.md` around lines 42 - 44, Update the versioning section in
docs/git-cicd.md to separate headver.json’s app-specific head values from
HEADVer tag creation performed by .github/workflows/headver-tagging.yml. Clarify
that post-deployment manual updates and Promote Main to Release
Branches/release-* branch promotion are not part of the current process, rather
than documenting them as required operational steps.

[coderabbitai]

🩺 Stability & Availability | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== files =="
git ls-files | rg '(^docs/.*multizone|^docs/git-cicd\.md$|^vercel\.json$|github\.workflows/.+\.(ya?ml))' || true

echo
echo "== docs snippets =="
sed -n '55,85p' docs/university-multizone-deployment.md 2>/dev/null || true
echo "---"
sed -n '32,52p' docs/git-cicd.md 2>/dev/null || true

echo
echo "== workflow references =="
rg -n "Promote Main to Release Branches|release-(web|admin|university)|production branch|productionBranch|Deployment|vercel|project" .github docs vercel.json 2>/dev/null || true

echo
echo "== vercel config =="
cat -n vercel.json 2>/dev/null || true

Repository: solid-connection/solid-connect-web

Length of output: 7254

---

1. Vercel Production Branch 전환을 배포 전제조건으로 명시하세요.

Vercel productionBranch는 저장소 파일이 아니라 각 Vercel Project 설정으로 정해집니다.

1) university-multizone-deployment.md의 production branch 안내 앞단에서 각 Project의 Vercel Settings > Git > Production Branch를 `main`으로 변경하는 순서를 추가하세요.
2) git-cicd.md의 `main` push → production 배포 설명 앞에 Vercel 설정 완료 조건을 명시하세요.

📍 Affects 2 files

• docs/university-multizone-deployment.md#L69-L75 (this comment)
• docs/git-cicd.md#L42-L44

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/university-multizone-deployment.md` around lines 69 - 75, The deployment
documentation must explicitly require updating Vercel settings before relying on
main-branch production deployments. In docs/university-multizone-deployment.md
lines 69-75, add steps before the production-branch guidance to set each Vercel
Project’s Settings > Git > Production Branch to main. In docs/git-cicd.md lines
42-44, state that this Vercel configuration must be completed before describing
main pushes as triggering production deployments.

---

🩺 Stability & Availability | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== files =="
git ls-files | sed -n '1,120p'

echo
echo "== target doc excerpt =="
if [ -f docs/university-multizome-deployment.md ]; then
  sed -n '1,120p' docs/university-multizone-deployment.md
else
  fd -a 'university-multizone-deployment\.md' . | while read -r f; do
    echo "-- $f"
    sed -n '1,120p' "$f"
  done
fi

echo
echo "== search vercel deployment docs/workflows =="
rg -n "Vercel|production branch|Production Branch|Vercl|release-web|release-admin|release-university|Promote Main to Release Branches|生产|배포" -S . --glob '!node_modules' --glob '!dist' --glob '!build' | sed -n '1,220p'

Repository: solid-connection/solid-connect-web

Length of output: 13736

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflows =="
for f in .github/workflows/*.yml .github/workflows/*.yaml; do
  [ -f "$f" ] || continue
  echo "-- $f"
  wc -l "$f"
  sed -n '1,220p' "$f" | sed -n '1,220p'
done

echo
echo "== git-cicd relevant =="
sed -n '1,90p' docs/git-cicd.md

echo
echo "== search release workflow files in history briefly =="
git ls-files .github/workflows | xargs -r -I{} sh -c 'echo "== {} =="; sed -n "1,220p" "{}" | grep -nE "release|release-(web|admin|university)|Promote|deploy|push_to_release|production branch|production branch" || true'

Repository: solid-connection/solid-connect-web

Length of output: 21343

---

1. Vercel Production Branch 설정 절차를 문서에 추가하세요.

문서는 production branch가 이미 main이라고 설명하지만, 배포 워크플로는 release 브랜치 갱신을 제거했을 뿐 Vercel 설정을 대체하지 않습니다.

- 각 프로젝트에서 `Settings > Git`의 Production Branch를 `main`으로 설정합니다.
- 전환 후 `main` push로 생산 환경에 배포되는지 각 프로젝트에서 확인합니다.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/university-multizone-deployment.md` around lines 69 - 75, 문서의 Vercel
production 배포 설명에 각 프로젝트의 설정 절차를 추가하세요. Main Web, Admin, University Web
Project에서 각각 Settings > Git의 Production Branch를 main으로 지정하고, 설정 전환 후 main push가
production 배포를 트리거하는지 확인하는 단계까지 명시하세요.