Release 2.1.1 - #848
Conversation
Back-merge v2.1.0 into develop
|
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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
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 |
Release 2.1.1
Version bump only (
pyproject.toml,uv.lock, Helm chartversion/appVersion,values.yamlimage tags,docker-compose.yamlimage pins), following the pattern from4cb7e7ff(2.1.0 bump).Not final yet: cut from
developbefore #847 (keep sources when the LLM omits the citation tag) has merged. This branch needsdevelopmerged back in (or the tag update replayed) once #847 lands, before this is tagged/released.Per
CONTRIBUTING.md: merge intomain, tagv2.1.1, then backmergerelease/2.1.1intodevelop.