[RELEASE] v0.0.3.2#269
Conversation
- 도메인 이전 전 PWA로 등록된 오래된 서비스워커가 사용자 브라우저에 남아 캐시된 구버전 페이지를 서빙하며 API 요청을 CSP로 차단하는 문제를 발견했습니다 - 페이지 로드 시 현재 origin에 등록된 서비스워커와 캐시를 자동으로 해제하는 ServiceWorkerCleanup을 추가했습니다 - 루트 레이아웃에 연결했습니다
…anup [FIX] 도메인 이전 전 PWA 서비스워커 잔재로 인한 API 요청 CSP 차단 수정
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 57 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Timo Performance ReportBundle Size — timo-web
Lighthouse — timo-web
Image Optimization — timo-web
측정 커밋: |
What's Changed
Full Changelog: v0.0.3.1...v0.0.3.2