Conversation
|
Warning Review limit reached
Next review available in: 52 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds ChangesEntry Lifecycle Hooks
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)Before-push flowsequenceDiagram
participant Caller
participant createUnhead
participant entriesBeforePush
Caller->>createUnhead: push(input, options)
createUnhead->>entriesBeforePush: callHook(input, options, shouldPush)
entriesBeforePush-->>createUnhead: update shouldPush
createUnhead-->>Caller: noop entry or active entry
Deferred disposal flowsequenceDiagram
participant ActiveHeadEntry
participant ClientAdapter
participant entriesBeforeDispose
participant DeferredPromises
ActiveHeadEntry->>ClientAdapter: dispose()
ClientAdapter->>entriesBeforeDispose: callHook(entry, defer)
entriesBeforeDispose-->>ClientAdapter: register PromiseLike values
ClientAdapter->>DeferredPromises: Promise.allSettled(values)
DeferredPromises-->>ClientAdapter: promises settle
ClientAdapter-->>ActiveHeadEntry: finalize disposal and invalidate head
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
📦 Bundle Size
All bundles (14)
📦 Runtime Dependencies✅ No runtime dependency changes All packages (10)
Skipped optional dependencies (114)
Production dependencies only. Peer dependencies and Unhead workspace packages are excluded. Skipped optional dependencies are unavailable on the CI platform. ⚡ Performance (directional)✅ No significant change (within CI noise) All benchmarks (14)
Baseline: main @ d9b3d2a · 2026-07-26 · gzipped is the headline size metric · perf is directional (shared-runner, gated) |
🔗 Linked issue
Nuxt integration workarounds: nuxt/nuxt#32100, nuxt/nuxt#35389
❓ Type of change
📚 Description
Adds
entries:beforePushso integrations can suppress an entry without replacinghead.push. Adds cliententries:beforeDisposeso integrations can keep outgoing head state until registered promises settle.Nuxt currently replaces
head.pushduring island rendering and returns a cast fake entry. It also replaces every entrydisposemethod to wait for page transitions. These typed hooks remove both monkey patches.Deferred disposal uses
Promise.allSettled, so failed navigation or suspense promises still release the entry. Both hooks are documented and covered by lifecycle tests.Testing:
pnpm lint,pnpm lint:docs,pnpm typecheck,pnpm build, andpnpm vitest run, with 1,784 passed and 8 skipped.