From 9ca9c91c8cd1b7c4f5f2ca00ff371cd52d0dd123 Mon Sep 17 00:00:00 2001
From: Hauser <housemecn@gmail.com>
Date: Thu, 24 Sep 2026 14:34:07 +0800
Subject: [PATCH] chore(release): prepare rustfs-uring 0.3.0

---
 CHANGELOG.md               | 5 ++++-
 Cargo.lock                 | 2 +-
 Cargo.toml                 | 2 +-
 README.md                  | 2 +-
 docs/rustfs-integration.md | 2 +-
 5 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6add655..0c432f2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -23,6 +23,8 @@ aims to follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.3.0] - 2026-09-24
+
 ### Added
 
 - Per-shard `shard_iowq_setup` startup snapshots of the existing best-effort
@@ -305,7 +307,8 @@ built. They are listed so nobody re-opens them without new evidence.
 [rustfs/backlog#1051]: https://github.com/rustfs/backlog/issues/1051
 [rustfs/backlog#1144]: https://github.com/rustfs/backlog/issues/1144
 [rustfs/backlog#1159]: https://github.com/rustfs/backlog/issues/1159
-[Unreleased]: https://github.com/rustfs/uring/compare/0.2.2...HEAD
+[Unreleased]: https://github.com/rustfs/uring/compare/0.3.0...HEAD
+[0.3.0]: https://github.com/rustfs/uring/compare/0.2.2...0.3.0
 [0.2.2]: https://github.com/rustfs/uring/compare/0.2.1...0.2.2
 [0.2.1]: https://github.com/rustfs/uring/compare/0.2.0...0.2.1
 [0.2.0]: https://github.com/rustfs/uring/compare/0.1.0...0.2.0
diff --git a/Cargo.lock b/Cargo.lock
index ba9f0ec..1e0bc4c 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -63,7 +63,7 @@ dependencies = [
 
 [[package]]
 name = "rustfs-uring"
-version = "0.2.2"
+version = "0.3.0"
 dependencies = [
  "io-uring",
  "libc",
diff --git a/Cargo.toml b/Cargo.toml
index 39121fc..5d422ce 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -14,7 +14,7 @@
 
 [package]
 name = "rustfs-uring"
-version = "0.2.2"
+version = "0.3.0"
 edition = "2024"
 rust-version = "1.98"
 license = "Apache-2.0"
diff --git a/README.md b/README.md
index b411960..9aea67a 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ When a caller drops the future of an in-flight read (an erasure-code quorum was
 
 ```toml
 [target.'cfg(target_os = "linux")'.dependencies]
-rustfs-uring = "0.2.2"
+rustfs-uring = "0.3.0"
 ```
 
 ## Usage
diff --git a/docs/rustfs-integration.md b/docs/rustfs-integration.md
index f75d912..e2f3761 100644
--- a/docs/rustfs-integration.md
+++ b/docs/rustfs-integration.md
@@ -9,7 +9,7 @@ application integration**. The reviewed RustFS main revision is
 ## Current production boundary
 
 The application's [ecstore dependency](https://github.com/rustfs/rustfs/blob/1880b42169bf26b15d8ca6bea3d8f1e4203b1bad/crates/ecstore/Cargo.toml#L230)
-still uses registry `rustfs-uring = "0.2.2"`; it does not yet consume the new
+still uses registry `rustfs-uring = "0.3.0"`; it does not yet consume the new
 `ReadLimits`, batch or shard-policy APIs. The [local backend](https://github.com/rustfs/rustfs/blob/1880b42169bf26b15d8ca6bea3d8f1e4203b1bad/crates/ecstore/src/disk/local.rs#L1087)
 keeps io_uring opt-in, a depth of 128 per shard and a 128 MiB read chunk cap.
 Configured shard counts multiply across disks; driver-local limits are not a