diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.3.0.0 — 2026-08-05
+
+### Breaking Changes
+
+- Moved onto the Keiki 0.9 / Keiro 0.11 cohort through `kioku-core` and `kioku-migrations`. The
+  bound is breaking; the schema effect is nothing. A database migrated by kioku 0.2.0.0 has no
+  pending migration on the next `kioku-migrate up` — every one of the 38 reports as already
+  applied, and `kioku-migrate verify` still reports `applied=38 pending=0 unknown=0`.
+
+### Changed
+
+- No change to planning, applying, verifying, repairing, Codd-history import, or read-model
+  registry reconciliation.
+
 ## 0.2.0.0 — 2026-07-30
 
 ### Breaking Changes
diff --git a/kioku-migrate.cabal b/kioku-migrate.cabal
--- a/kioku-migrate.cabal
+++ b/kioku-migrate.cabal
@@ -1,6 +1,6 @@
 cabal-version:   3.0
 name:            kioku-migrate
-version:         0.2.0.0
+version:         0.3.0.0
 synopsis:        The kioku schema migration entry point
 description:
   Applies kioku's migration chain and then reconciles keiro's read-model
@@ -49,8 +49,8 @@
     , base                    >=4.21     && <5
     , bytestring              >=0.12     && <0.13
     , hasql                   >=1.10     && <1.11
-    , kioku-core              ^>=0.2.0.0
-    , kioku-migrations        ^>=0.2.0.0
+    , kioku-core              ^>=0.3.0.0
+    , kioku-migrations        ^>=0.3.0.0
     , kiroku-store            ^>=0.3.0.1
     , optparse-applicative    >=0.17     && <0.20
     , pg-migrate              ^>=1.1.0.0