chore(release): v0.1.13

[Andrei Kvapil (kvaps)]

What

Cut the v0.1.13 release: add the CHANGELOG entry for the release-gate hardening campaign (≈10 product bug fixes + read-after-write reliability + honest-CI/test infrastructure). Documentation only.

Why

origin/main has accumulated the campaign fixes since v0.1.12 and passed an independent release-gate (GO) plus a completed 24h ZFS-thick burn-in. This records the release notes; the tag v0.1.13 (pushed after merge) publishes the images.

Scope

CHANGELOG.md only — no code, no data-path change. Candidate commit 5db10bd carries a release-gate GO; this docs-only addition is data-path-identical.

Summary by CodeRabbit

• Bug Fixes

  • Fixed multiple backend race conditions and improved data consistency and atomicity in distributed scenarios.

• Known Issues

  • Rapid operations on certain multi-replica configurations may encounter issues.

• Documentation

  • Changelog updated for v0.1.13 with fixes, known issues, and testing infrastructure updates.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5ffd94b8-c105-4875-9b82-a71e8761c4bf

📥 Commits

Reviewing files that changed from the base of the PR and between 5db10bd and de6716c.

📒 Files selected for processing (1)

• CHANGELOG.md

---

📝 Walkthrough

Walkthrough

A new changelog entry for v0.1.13 (2026-06-15) is prepended to CHANGELOG.md. It covers 29 added lines across three sections: Fixed (race and correctness fixes), Known issues (one concurrency edge case), and Testing & infrastructure (CI and harness updates).

Changes

v0.1.13 Changelog Entry

Layer / File(s)	Summary
v0.1.13 release notes CHANGELOG.md	Adds the v0.1.13 heading with a Fixed list of race/correctness closures, a Known issues entry for rapid late vd c on multi-replica scenarios, and Testing & infrastructure items for CI endurance and harness/coverage fixes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 A changelog grows by twenty-nine lines,
With races corrected and neatly aligned,
Known issues confessed with a candid refrain,
And CI runs honest through sunshine and rain.
Hop to v0.1.13, the burrow's been refined! 🌿

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(release): v0.1.13' directly and clearly describes the main change: a release of version 0.1.13, which matches the PR's primary objective of releasing blockstor v0.1.13.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.1.13

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the CHANGELOG.md file to document the release of version v0.1.13, detailing various bug fixes, known issues, and testing/infrastructure improvements. The review feedback suggests a minor grammatical correction to remove unnecessary hyphenation in the release description.

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.

[gemini-code-assist]

The phrase re-verify-everything is used as a verb phrase here and should not be hyphenated. It should be written as re-verify everything.

Suggested change

Release-gate hardening release. A full independent acceptance gate (default NO-GO, re-verify-everything against the live Talos+QEMU stand plus a completed 24-hour ZFS-thick endurance burn-in) was run against this candidate; the fixes below were mined and validated over that campaign. Primary backend focus is ZFS thick. Every fix is pinned at L1 unit and, where operator-CLI-reachable, L6 cli-matrix + L7 replay, and was exercised on the live stand.

Release-gate hardening release. A full independent acceptance gate (default NO-GO, re-verify everything against the live Talos+QEMU stand plus a completed 24-hour ZFS-thick endurance burn-in) was run against this candidate; the fixes below were mined and validated over that campaign. Primary backend focus is ZFS thick. Every fix is pinned at L1 unit and, where operator-CLI-reachable, L6 cli-matrix + L7 replay, and was exercised on the live stand.