@prisma/orm-mongo 8.0.0-rc.18-dev.5 → 8.0.0-rc.18-dev.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/orm-mongo",
-  "version": "8.0.0-rc.18-dev.5",
+  "version": "8.0.0-rc.18-dev.6",
   "license": "Apache-2.0",
   "type": "module",
   "sideEffects": false,
@@ -10,18 +10,18 @@
     "skills"
   ],
   "dependencies": {
-    "@prisma/orm-family-mongo": "8.0.0-rc.18-dev.5",
-    "@prisma/orm-framework": "8.0.0-rc.18-dev.5",
-    "@prisma/orm-target-mongo": "8.0.0-rc.18-dev.5",
-    "@prisma/orm-toolchain": "8.0.0-rc.18-dev.5",
+    "@prisma/orm-family-mongo": "8.0.0-rc.18-dev.6",
+    "@prisma/orm-framework": "8.0.0-rc.18-dev.6",
+    "@prisma/orm-target-mongo": "8.0.0-rc.18-dev.6",
+    "@prisma/orm-toolchain": "8.0.0-rc.18-dev.6",
     "mongodb-connection-string-url": "^7.0.1",
     "pathe": "^2.0.3",
     "tinyglobby": "^0.2.17"
   },
   "devDependencies": {
-    "@internal/mongo": "8.0.0-rc.18-dev.5",
-    "@repo/tsconfig": "8.0.0-rc.18-dev.5",
-    "@repo/tsdown": "8.0.0-rc.18-dev.5",
+    "@internal/mongo": "8.0.0-rc.18-dev.6",
+    "@repo/tsconfig": "8.0.0-rc.18-dev.6",
+    "@repo/tsdown": "8.0.0-rc.18-dev.6",
     "tsdown": "0.22.14",
     "typescript": "5.9.3"
   },

package/skills/prisma-8/SKILL.md

@@ -15,7 +15,7 @@ description: >-
   ORM 7 or earlier (schema.prisma + @prisma/client).
 metadata:
   library: '@prisma/orm-mongo'
-  library_version: '8.0.0-rc.18-dev.5'
+  library_version: '8.0.0-rc.18-dev.6'
   version: '2026-09-12'
 ---
 

package/skills/prisma-8/references/runtime.md

@@ -176,6 +176,7 @@ The concept: the runtime runs every statement and every transaction as an **acti
 
 - Lifecycle events, for every activity: `activityStarted(activity, ctx)`, `activityEnded(activity, result, ctx)` and `activityFinalized(activity, result, ctx)`. Check `activity.kind` (`'statement'` or `'transaction'`) at the top. `activityEnded` fires when the act ends: for a statement with `result.outcome` (`'succeeded'`, `'failed'`, or `'stopped'` when the caller stopped reading), `result.latencyMs`, `result.source` (`'driver'`, or `'middleware'` for a cache hit) and `result.rowCount` or `result.stats` according to `result.returns`. `activityFinalized` fires once the effects are final, with `result.outcome` `'committed'`, `'rolled-back'` or `'unknown'`: right after the end outside a transaction, and when the transaction ends inside one. Every statement that started is finalized, even one blocked before it ran.
 - Interceptors, for statements: `beforeEncode(plan, ctx, params)` before parameters are encoded (throw to block the statement), `intercept.onQuery` / `intercept.onExecute` to supply a result instead of running it, and `onRow(row, plan, ctx)` for each driver row.
+- Client activities: a client library can start an activity of its own kind, which contains a hyphen, such as `orm-call`, and send its statements beneath it. A middleware sees it through the same lifecycle events, with `activity.kind` set to that kind and `ctx.parent` of its statements pointing at it, and can supply its result through `intercept.onActivity(activity, ctx)`. Outside a transaction it is finalized right after it ends; inside one, when the transaction ends, after its statements. No built-in client starts one yet, so a middleware that handles only `'statement'` and `'transaction'` should ignore other kinds rather than fail on them.
 
 Every hook of one activity receives the same `ctx`. Keep per-statement state in `ctx.state(key)` (use a `Symbol()` key); `activity.id` identifies the activity, and `ctx.parent` is the enclosing transaction's context. There is no separate telemetry package — observe statements with `activityEnded`. The `SqlMiddleware` type comes from `@prisma/orm-postgres/family-runtime`. `examples/prisma-8-demo/src/prisma/slow-query-warning.ts` is the canonical example: