fix: Harden V2-to-V3 third-party migration for safe apply and reliable scans#1710
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
…1702) Co-authored-by: Cursor <cursoragent@cursor.com>
…ars (#1703) Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
#1709) Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reached
Next review available in: 4 seconds 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: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (6)
📒 Files selected for processing (25)
✨ 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 |
Summary
Landing the
v3-migration-hardeningintegration branch intov3-betaas one squash commit. This hardens the V2→V3 third-party migration path across write safety, rewrite correctness, wizard UX, temporary skill guidance, Go skill install cleanup, and scan exclusions.Included changes (PR1–PR9)
referencessurgicallyUser Impact
Third-party migration is safer to run: failed applies roll back, encoding and asmdef formatting stay intact, the wizard asks before rewriting and shows which files change, and scans no longer hang on symlink cycles or dive into Unity-ignored folders.
Test plan
v3-beta(Build and Test / Unity Compile Check) — final gateMade with Cursor