fix: Vercel 배포 환경에서 웹 버전이 표시되지 않는 문제 수정 - #275
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No description provided. |
|
Warning Review limit reached
More reviews will be available in 39 minutes and 49 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
ChangesWeb Version 주입 방식 교체
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 `@apps/web/config/getWebVersion.mjs`:
- Around line 17-18: The getWebVersion.mjs file reads environment variables
(VERCEL, VERCEL_GIT_COMMIT_REF, VERCEL_GIT_REPO_OWNER, VERCEL_GIT_REPO_SLUG, and
GITHUB_TOKEN) but these are not declared as dependencies in the Turbo cache
configuration. Add these environment variable keys to the env or globalEnv field
of the affected tasks (build and dev) in turbo.json to ensure that changes to
these environment variables properly invalidate the cache and prevent stale
version values from being reused.
- Around line 31-34: The fetch call to the GitHub API endpoint
(https://api.github.com/repos/${owner}/${repo}/tags?per_page=100) lacks a
timeout configuration, which can cause the build to hang indefinitely during
network delays or API unresponsiveness. Add an AbortController with an explicit
timeout signal to the fetch request options (alongside the existing headers).
Set an appropriate timeout duration (e.g., 5-10 seconds) to ensure the fetch
fails fast and allows the build process to continue or fail gracefully instead
of blocking the next.config evaluation.
🪄 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
Run ID: 219cc2ec-587b-47c4-92c6-7702d8b73d43
📒 Files selected for processing (4)
apps/web/config/getWebVersion.mjsapps/web/next.config.mjsapps/web/package.jsonapps/web/scripts/prebuild.mjs
💤 Files with no reviewable changes (2)
- apps/web/scripts/prebuild.mjs
- apps/web/package.json
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@apps/web/config/getWebVersion.mjs`:
- Around line 31-33: The getWebVersion.mjs tag lookup only fetches the first 100
GitHub tags, so web-* selection can miss the newest release when there are more
than 100 tags. Update the tag retrieval in getWebVersion to either paginate
through the GitHub “List repository tags” results until all tags are collected
or switch to a direct latest-tag lookup approach, then keep the existing version
चयन logic working against the complete tag set.
🪄 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
Run ID: 4e544c67-f97c-4c7d-9f75-ded92c172f3e
📒 Files selected for processing (2)
apps/web/config/getWebVersion.mjsturbo.json
* fix: 웹 버전 확인 전 반드시 git fetch 하도록 설정 * chore: vercel 배포 로그 확인 * chore: git open api로 웹 버전 정보 확인하도록 변경 * chore: turbo 캐시 의존에 누락된 환경변수 추가 * chore: github api로 version 가져올 때 timeout 10초 제한 추가 * refactor: 가장 최신 웹 버전 태그 가져오도록 수정
작업 요약
작업 내용
문제점
NEXT_PUBLIC_WEB_VERSION)이 비어 footer가 안 보임prebuild는 로컬 git 태그 →.env.local주입 방식이라 Vercel shallow clone 환경과 맞지 않음원인 분석
git describe로web-v*태그를 안정적으로 못 읽음해결 방법
prebuild제거,next.configasync에서getWebVersion으로 빌드 시 env 주입VERCEL_GIT_COMMIT_REF파싱, 브랜치 배포면 GitHub API로 최신web-v*조회git describe→git tag -lfallbackclose #270
Summary by CodeRabbit
릴리스 노트
리팩터
NEXT_PUBLIC_WEB_VERSION이 채워지도록 개선변경사항
빌드/구성