@shivaedev/effect-changes-prisma 0.2.0 → 0.2.1

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.2.1 - 2026-09-28
+
+### Changed
+
+- Pin the `@prisma/client` peer dependency to exactly 7.10.0, the version the
+  package is now tested against, instead of 7.9.1.
+
 ## 0.2.0 - 2026-09-26
 
 ### Added

package/README.md

@@ -138,9 +138,9 @@ const violations = checkCoverage({
 - The client handed to `use` wraps write methods of mapped models, so their results are plain promises: pass them to `transaction`, not to the array form of `$transaction`, and do not chain fluent relation calls on them. Calling `$transaction` on that client runs outside the binding; use `transaction`.
 - A relation write nested in `data` records only the top-level model.
 - Prisma's interactive transaction timeout (5 seconds by default) still applies; pass `{ timeout }` to `transaction` for a longer one.
-- The client's timeout is read from Prisma's internal client configuration, which Prisma `7.9.1` keeps on the client. If a later Prisma moves it, `transaction` sets no deadline of its own, and a body that outlives Prisma's timeout stops at its first query after the transaction closes; pass `{ timeout }` to have it interrupted on time.
+- The client's timeout is read from Prisma's internal client configuration, which Prisma `7.10.0` keeps on the client. If a later Prisma moves it, `transaction` sets no deadline of its own, and a body that outlives Prisma's timeout stops at its first query after the transaction closes; pass `{ timeout }` to have it interrupted on time.
 - `checkCoverage` matches tables by name, not by schema.
 - `writtenTables` does not see a `TRUNCATE` inside the test transaction: `TRUNCATE` resets the transaction's insert, update and delete counts in `pg_stat_xact_user_tables`, so they fall back to the baseline, and a table that was written and then truncated counts as unwritten.
 - Delivery is in-process, as for every effect-changes channel.
 
-Tested with Prisma `7.9.1` and `@prisma/adapter-pg` on PostgreSQL 18, and Effect `4.0.0-rc.112`.
+Tested with Prisma `7.10.0` and `@prisma/adapter-pg` on PostgreSQL 18, and Effect `4.0.0-rc.112`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shivaedev/effect-changes-prisma",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Commit-bound change channels for Prisma Classic: automatic change recording, publish after $transaction commits, and a test-time coverage check",
   "type": "module",
   "license": "MIT",
@@ -40,16 +40,16 @@
     "@shivaedev/effect-changes": "0.1.0"
   },
   "peerDependencies": {
-    "@prisma/client": "7.9.1",
+    "@prisma/client": "7.10.0",
     "effect": "4.0.0-rc.112"
   },
   "devDependencies": {
-    "@prisma/adapter-pg": "7.9.1",
-    "@prisma/client": "7.9.1",
+    "@prisma/adapter-pg": "7.10.0",
+    "@prisma/client": "7.10.0",
     "@types/node": "24.10.1",
     "@typescript/native": "npm:typescript@7.0.2",
     "effect": "4.0.0-rc.112",
-    "prisma": "7.9.1",
+    "prisma": "7.10.0",
     "typescript": "npm:@typescript/typescript6@6.0.2",
     "vitest": "4.1.9"
   },