Deploy->master - #76
Conversation
|
Warning Review limit reached
Next review available in: 16 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: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (30)
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 |
The lockfile was regenerated on macOS, which resolved the oxc wasm bindings' @emnapi optional deps to versions the Linux CI runner's npm ci rejected (Missing @emnapi/core@1.11.2 / @emnapi/runtime@1.11.2). Regenerated under the CI toolchain (node 24 / npm 11.16.0 on linux) and verified npm ci passes; retains both linux and darwin bindings. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Nuxt 4 depends on vue-router@^5.1.0 and generates a tsconfig that references the vue-router/volar/sfc-route-blocks Volar plugin, which only exists in vue-router 5.x. The project pinned ^4.2.5, so a phantom top-level vue-router@4.6.4 (no ./volar export) shadowed Nuxt's nested 5.1.0 and broke `nuxt typecheck` with ERR_PACKAGE_PATH_NOT_EXPORTED. The app already runs on v5 at runtime via Nuxt. Verified npm ci + nuxt typecheck pass on the CI toolchain (node 24 / npm 11.16.0, linux). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The "Improve mobile usability" refactor (7447e92) placed </span> and #{{ id }} adjacent and moved the gap to a me-1 margin, which silently dropped the space from the item's accessible name ("Feedback:#555" instead of "Feedback: #555"), failing the review.spec ARIA snapshot. Restore a real space between the type label and id (the space now provides the visual gap, so me-1 is removed). Verified the e2e test passes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
3 participants
Merge of
deploybranch changes tomaster