diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,16 @@
 # Changelog
 
+## 0.4.0.0 — 2026-08-17
+
+### Breaking Changes
+
+- The composed plan gains `kioku/0012-relocate-projections-to-kioku-schema`, which moves Kioku's
+  seven projections out of the `kiroku` schema into a dedicated `kioku` one. `up` and `status`
+  now report 53 migrations (kiroku 11, keiro 30, kioku 12). Run it with writers stopped and before
+  the new application binary starts; `up` reconciles the Keiro read-model registry to the new
+  memory v3 / session v5 / turn v3 identities afterwards, as it always has. See
+  `docs/user/upgrading-to-the-kioku-schema.md`.
+
 ## 0.3.0.0 — 2026-08-05
 
 ### 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.3.0.0
+version:         0.4.0.0
 synopsis:        The kioku schema migration entry point
 description:
   Applies kioku's migration chain and then reconciles keiro's read-model
@@ -49,9 +49,9 @@
     , base                    >=4.21     && <5
     , bytestring              >=0.12     && <0.13
     , hasql                   >=1.10     && <1.11
-    , kioku-core              ^>=0.3.0.0
-    , kioku-migrations        ^>=0.3.0.0
-    , kiroku-store            ^>=0.3.0.1
+    , kioku-core              ^>=0.4.0.0
+    , kioku-migrations        ^>=0.4.0.0
+    , kiroku-store            ^>=0.8.0.0
     , optparse-applicative    >=0.17     && <0.20
     , pg-migrate              ^>=1.1.0.0
     , pg-migrate-cli          ^>=1.1.0.0