@prisma/orm-mongo 8.0.0-rc.17-dev.34 → 8.0.0-rc.17-dev.36

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/orm-mongo",
-  "version": "8.0.0-rc.17-dev.34",
+  "version": "8.0.0-rc.17-dev.36",
   "license": "Apache-2.0",
   "type": "module",
   "sideEffects": false,
@@ -10,18 +10,18 @@
     "skills"
   ],
   "dependencies": {
-    "@prisma/orm-family-mongo": "8.0.0-rc.17-dev.34",
-    "@prisma/orm-framework": "8.0.0-rc.17-dev.34",
-    "@prisma/orm-target-mongo": "8.0.0-rc.17-dev.34",
-    "@prisma/orm-toolchain": "8.0.0-rc.17-dev.34",
+    "@prisma/orm-family-mongo": "8.0.0-rc.17-dev.36",
+    "@prisma/orm-framework": "8.0.0-rc.17-dev.36",
+    "@prisma/orm-target-mongo": "8.0.0-rc.17-dev.36",
+    "@prisma/orm-toolchain": "8.0.0-rc.17-dev.36",
     "mongodb-connection-string-url": "^7.0.1",
     "pathe": "^2.0.3",
     "tinyglobby": "^0.2.17"
   },
   "devDependencies": {
-    "@internal/mongo": "8.0.0-rc.17-dev.34",
-    "@repo/tsconfig": "8.0.0-rc.17-dev.34",
-    "@repo/tsdown": "8.0.0-rc.17-dev.34",
+    "@internal/mongo": "8.0.0-rc.17-dev.36",
+    "@repo/tsconfig": "8.0.0-rc.17-dev.36",
+    "@repo/tsdown": "8.0.0-rc.17-dev.36",
     "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.17-dev.34'
+  library_version: '8.0.0-rc.17-dev.36'
   version: '2026-09-12'
 ---
 

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

@@ -293,7 +293,7 @@ Order matters: `beforeEncode` runs in registration order for every middleware be
 
 ## Workflow — Configure the connection
 
-The concept: the runtime takes one of three binding shapes — `url`, `pg` (a pre-constructed `pg.Pool` or `pg.Client`), or `binding` (an explicit kind tag). They're mutually exclusive. The `pg` form is for projects that already manage their own pool (e.g. a Lambda layer); `url` is the default. Pool tuning is `poolOptions.connectionTimeoutMillis` / `poolOptions.idleTimeoutMillis` — *not* `driverOptions`. Reads are buffered by default; setting `cursor` (`{ batchSize: 100 }`; `{}` or `{ batchSize: undefined }` for batches of 100; a `batchSize` that is not a positive integer fails the factory call) makes them stream through a server-side cursor, and there is no flag that turns cursors off (see `references/queries.md` § *Streaming*). `postgresServerless()` takes the same `cursor` option.
+The concept: the runtime takes one of three binding shapes — `url`, `pg` (a pre-constructed `pg.Pool` or `pg.Client`), or `binding` (an explicit kind tag). They're mutually exclusive. The `pg` form is for projects that already manage their own pool (e.g. a Lambda layer); `url` is the default. Pool tuning is `poolOptions.connectionTimeoutMillis` / `poolOptions.idleTimeoutMillis` — *not* `driverOptions`. Reads are buffered by default; setting `cursor` (`{ batchSize: 100 }`; `{}` or `{ batchSize: undefined }` for batches of 100; a `batchSize` that is not a positive integer fails the factory call) makes them stream through a server-side cursor, and there is no flag that turns cursors off (see `references/queries.md` § *Streaming*). `postgresServerless()` takes the same `cursor` option. Pass `log` (an object with `info`, `warn`, `error` and an optional `debug`; `console` works, and the type is `Log` from `@prisma/orm-postgres/family-runtime`) to receive what the runtime logs: the marker-verification warnings `CONTRACT.MARKER_MISSING` and `CONTRACT.MARKER_MISMATCH` from the first query, the warnings `lints()` emits for rules whose severity is `warn`, and the errors a middleware's `activityEnded` or `activityFinalized` hook throws, which the runtime logs and swallows. If `log` has a `debug` method, it also receives debug events, for example when a middleware intercepts a statement. `budgets()` violations never reach `log`: the client runs its runtime in strict mode, so a violation throws, until the client exposes `mode` (TML-3567). Without `log`, the runtime drops these events. `postgresServerless()`, `sqlite()` and `supabase()` take the same option.
 
 ```typescript
 // Default — URL string, factory constructs the pool.
@@ -305,6 +305,7 @@ postgres<Contract>({
     idleTimeoutMillis: 30_000,
   },
   // cursor: { batchSize: 100 },  // optional — stream reads in batches instead of buffering
+  // log: console,                // optional — receive marker and lints() warnings
 });
 
 // BYO pool — pass a pg.Pool you already created.