Skip to content

chore(release): v0.1.17#179

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
release/v0.1.17
Jul 4, 2026
Merged

chore(release): v0.1.17#179
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
release/v0.1.17

Conversation

@kvaps

Copy link
Copy Markdown
Member

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.17 after merge triggers the release pipeline (3 ghcr images + GitHub Release from this CHANGELOG section).

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@coderabbitai

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kvaps, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: aa66397f-c09e-4e33-a002-b4388b77a683

📥 Commits

Reviewing files that changed from the base of the PR and between 670b611 and 0c8993a.

📒 Files selected for processing (1)
  • CHANGELOG.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v0.1.17

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@kvaps
Andrei Kvapil (kvaps) merged commit 1ca6fa6 into main Jul 4, 2026
8 checks passed

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant