chore(release): v0.1.17#179
Conversation
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
|
Warning Review limit reached
Next review available in: 55 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. ✨ 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 |
There was a problem hiding this comment.
Code Review
This pull request updates the CHANGELOG.md file to document the changes introduced in version v0.1.17. These changes include bug fixes related to preserving DRBD minor/device identity, validating layer stacks on resource group modifications, and enforcing volume size limits during resizing, as well as integration test adjustments and deferred items. There are no review comments, so I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Cut v0.1.17 — adversarial-hardening release from the red/blue loop. Three modify-bypasses-create-validation fixes (#175 VD-resize size bounds / Bug 155-class, #177 Bug 433 VD-modify DRBDMinor carry-across, #178 Bug 434 rg-modify layer_stack validation) + CI-flake fix (#176). DRBD-kernel tier + N3/N4 parity/product questions deferred to the live stand. Tagging
v0.1.17after merge triggers the release pipeline (3 ghcr images + GitHub Release from this CHANGELOG section).