shikumi-trace 0.3.0.1 → 0.3.0.2
raw patch · 2 files changed
+17/−9 lines, 2 filesdep ~baikaidep ~shikumidep ~shikumi-cachePVP ok
version bump matches the API change (PVP)
Dependency ranges changed: baikai, shikumi, shikumi-cache, shikumi-trace
API changes (from Hackage documentation)
Files
- CHANGELOG.md +8/−0
- shikumi-trace.cabal +9/−9
CHANGELOG.md view
@@ -2,6 +2,14 @@ ## Unreleased +## 0.3.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.3.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-trace.cabal view
@@ -1,6 +1,6 @@ cabal-version: 3.4 name: shikumi-trace-version: 0.3.0.1+version: 0.3.0.2 synopsis: Hierarchical tracing, observability, and deterministic replay for shikumi (EP-7) @@ -58,7 +58,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, bytestring >=0.11 && <0.13, containers >=0.6 && <0.9,@@ -67,8 +67,8 @@ generic-lens >=2.2 && <2.4, lens ^>=5.3, scientific >=0.3 && <0.4,- shikumi ^>=0.4.0.0,- shikumi-cache ^>=0.2.0.1,+ shikumi ^>=0.4.1.1,+ shikumi-cache ^>=0.2.0.2, text ^>=2.1, time >=1.12 && <1.17, vector >=0.13 && <0.14,@@ -83,7 +83,7 @@ build-depends: base,- shikumi-trace ^>=0.3.0.1,+ shikumi-trace ^>=0.3.0.2, test-suite shikumi-trace-test import: common-options@@ -101,16 +101,16 @@ build-depends: QuickCheck, aeson,- baikai >=0.7.1.0 && <0.8,+ baikai >=0.8.0.0 && <0.9, base, bytestring, containers, effectful, generic-lens, lens ^>=5.3,- shikumi ^>=0.4.0.0,- shikumi-cache ^>=0.2.0.1,- shikumi-trace ^>=0.3.0.1,+ shikumi ^>=0.4.1.1,+ shikumi-cache ^>=0.2.0.2,+ shikumi-trace ^>=0.3.0.2, tasty, tasty-hunit, tasty-quickcheck,