ci: 앱별 태그와 PR 라벨링 수정

[manNomi]

관련 이슈

• 없음

작업 내용

• PR 자동 라벨러가 web, admin, university 세 앱 변경을 모두 감지하도록 수정했습니다.
• PR synchronize 시 기존 앱 라벨이 stale 상태로 남지 않도록 관리 라벨을 제거 후 현재 변경 파일 기준으로 다시 부여하게 했습니다.
• 앱별 HeadVer 태그 생성 스크립트를 추가하고, 릴리즈 태그를 web-v..., admin-v..., university-v... 형태로 분리했습니다.
• 릴리즈 워크플로우에서 target별 release branch와 main 사이의 앱/공유 변경사항을 확인한 뒤 필요한 앱만 태그/릴리즈/브랜치 승격을 수행하도록 수정했습니다.
• 누락되어 있던 apps/admin/headver.json을 추가했습니다.

특이 사항

• 기존 루트 headver.json fallback을 제거해 v0... 형태의 잘못된 공통 태그가 생성되지 않도록 했습니다.
• all target은 web, admin, university를 matrix로 검사하지만, 각 앱 또는 공유 영역 변경이 있는 target만 릴리즈합니다.
• 로컬에 actionlint가 없어 GitHub Actions 전용 정적 검사는 실행하지 못했습니다.

리뷰 요구사항 (선택)

• 앱별 태그 prefix(web-v, admin-v, university-v)가 운영에서 기대하는 이름인지 확인 부탁드립니다.
• 공유 변경 경로를 packages/, 루트 패키지/락파일, turbo.json, vercel.json, scripts/로 잡은 기준이 충분한지 확인 부탁드립니다.

검증

• bash -n .github/scripts/create-headver-tag.sh
• ruby -e 'require "yaml"; %w[.github/workflows/pr-auto-label.yml .github/workflows/headver-tagging.yml .github/workflows/release.yml].each { |path| YAML.load_file(path); puts "#{path}: ok" }'
• TARGET=web CREATE_TAG=false YYWW_OVERRIDE=2699 bash .github/scripts/create-headver-tag.sh
• TARGET=admin CREATE_TAG=false YYWW_OVERRIDE=2699 bash .github/scripts/create-headver-tag.sh
• TARGET=university CREATE_TAG=false YYWW_OVERRIDE=2699 bash .github/scripts/create-headver-tag.sh
• 앱별 path regex dry-run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
solid-connect-university-web	Ready	Preview, Comment	Jul 6, 2026 3:11am
solid-connect-web-admin	Ready	Preview, Comment	Jul 6, 2026 3:11am
solid-connection-web	Ready	Preview, Comment	Jul 6, 2026 3:11am

[coderabbitai]

Warning

Review limit reached

@manNomi, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 15 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 4523de3e-6069-4853-9be5-323a0f7106c4

📥 Commits

Reviewing files that changed from the base of the PR and between 78632fa and b6137bd.

📒 Files selected for processing (5)

• .github/scripts/create-headver-tag.sh
• .github/workflows/headver-tagging.yml
• .github/workflows/pr-auto-label.yml
• .github/workflows/release.yml
• apps/admin/headver.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/github-app-tagging

---

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