Release v1.3.0: Docker container isolation - #99
Conversation
|
Warning Review limit reached
Next review available in: 33 seconds You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Repository UI (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
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 |
Bundler CI fails when the gemspec version changes without updating the PATH entry in Gemfile.lock.
Hard-coded 1.2.0 expectation broke CI after the version bump.
Summary
SkillBench::VERSIONto 1.3.0[Unreleased]isolation notes to## [1.3.0] - 2026-08-08Context
Milestone
container-isolation-v1is closed. Issues #89/#90 closed as shipped.Test plan
v1.3.0, GitHub release, gem push