kioku-migrate 0.4.1.0 → 0.5.0.0

raw patch · 2 files changed

+23/−3 lines, 2 filesdep ~kioku-coredep ~kioku-migrations

Dependency ranges changed: kioku-core, kioku-migrations

Files

• CHANGELOG.md +20/−0
• kioku-migrate.cabal +3/−3

@@ -1,5 +1,25 @@ # Changelog +## 0.5.0.0 — 2026-08-22++### Breaking Changes++- The composed plan includes the corrected Kioku `0011` payload. A database that already applied+  `0011` with Kioku 0.4.0.0 or 0.4.1.0 must run+  `kioku-migrations/ledger-fixups/2026-08-19-rebaseline-0011-checksum.sql` before this executable's+  first `up` or `verify`; a database where `0011` is pending needs no preflight action. The next+  release must use the 0.5.0.0 series.++### Changed++- The composed Keiro migration dependency is now 0.14.0.0 and includes `keiro/0031`. `up`,+  `status`, and `verify` now report 55 migrations: Kiroku 11, Keiro 31, and Kioku 13.++### Fixed++- A single composed `up` no longer leaves the migration connection's `search_path` pinned to the+  Kiroku schema before control reaches an application-owned component.+ ## 0.4.1.0 — 2026-08-18  ### Changed

@@ -1,6 +1,6 @@ cabal-version:   3.0 name:            kioku-migrate-version:         0.4.1.0+version:         0.5.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.4.1.0-    , kioku-migrations        ^>=0.4.1.0+    , kioku-core              ^>=0.5.0.0+    , kioku-migrations        ^>=0.5.0.0     , kiroku-store            ^>=0.8.0.0     , optparse-applicative    >=0.17     && <0.20     , pg-migrate              ^>=1.1.0.0