Re-pin keep v0.7.4 (OPRF unlock holder failover)#95
Conversation
Signed-off-by: Kyle 🐆 <kyle@privkey.io>
|
Warning Review limit reached
Next review available in: 26 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 (1)
✨ 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 |
Re-pin the
keepinput from v0.7.3 to v0.7.4.v0.7.4 adds in-attempt holder failover to the threshold-OPRF boot-unlock (privkeyio/keep#738): when a sampled holder is momentarily unreachable, the box excludes it and re-samples another eligible holder within the same unlock instead of failing the boot closed. This directly hardens the multi-geo / flaky-remote-holder case that the oprf-gate and oprf-unlock VM tests exercise.
Lock updated to rev 2ad42c5 (tag v0.7.4). No keep-node source change.