packages feed

shikumi-cache 0.2.0.1 → 0.2.0.2

raw patch · 2 files changed

+14/−6 lines, 2 filesdep ~baikaidep ~shikumidep ~shikumi-cachePVP ok

version bump matches the API change (PVP)

Dependency ranges changed: baikai, shikumi, shikumi-cache

API changes (from Hackage documentation)

Files

CHANGELOG.md view
@@ -2,6 +2,14 @@  ## Unreleased +## 0.2.0.2 — 2026-10-16++### Changed++- Require the compatible Shikumi patch releases built against Baikai 0.8.++- Upgrade `mori://shinzui/baikai/packages/baikai` to `>=0.8.0.0 && <0.9`.+ ## 0.2.0.1 — 2026-10-05  - Move the dependency on `mori://shinzui/baikai/packages/baikai` to `>=0.7.1.0 && <0.8` and widen the `effectful` bound to `>=2.6 && <2.8`, so both effectful 2.6 and 2.7 are supported (effectful 2.7 needs `baikai-effectful` 0.4.0.2, effectful 2.6 needs 0.4.0.1). Bounds only; no source changed.
shikumi-cache.cabal view
@@ -1,6 +1,6 @@ cabal-version: 3.4 name: shikumi-cache-version: 0.2.0.1+version: 0.2.0.2 synopsis: Content-addressed response caching for shikumi (EP-6) category: AI description:@@ -51,7 +51,7 @@    build-depends:     aeson >=2.2 && <2.3,-    baikai >=0.7.1.0 && <0.8,+    baikai >=0.8.0.0 && <0.9,     base >=4.20 && <5,     blake3 >=0.3 && <0.4,     bytestring >=0.11 && <0.13,@@ -61,7 +61,7 @@     generic-lens >=2.2 && <2.4,     lens ^>=5.3,     scientific >=0.3 && <0.4,-    shikumi ^>=0.4.0.0,+    shikumi ^>=0.4.1.1,     stm >=2.5 && <2.6,     text ^>=2.1,     time >=1.12 && <1.17,@@ -78,7 +78,7 @@    build-depends:     aeson,-    baikai >=0.7.1.0 && <0.8,+    baikai >=0.8.0.0 && <0.9,     base,     bytestring,     containers,@@ -89,8 +89,8 @@     generic-lens,     lens,     process,-    shikumi ^>=0.4.0.0,-    shikumi-cache ^>=0.2.0.1,+    shikumi ^>=0.4.1.1,+    shikumi-cache ^>=0.2.0.2,     stm,     tasty,     tasty-hunit,