@prisma/orm-mongo 8.0.0-rc.16-dev.3 → 8.0.0-rc.16-dev.4

package/package.json

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

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

@@ -84,7 +84,7 @@ The single source of truth: read the envelope, find the row by `code`, follow th
 | `CONTRACT.VALIDATION_FAILED` | `contract emit`, `db *` | Re-run `pnpm prisma contract emit` after fixing the contract source named in `where.path`; `meta.errors` lists the issues. See `references/contract.md`. |
 | `CONFIG.DB_CONNECTION_REQUIRED` | `db *`, `db migrate`, `migration status` | Pass `--db <url>` or set `db.connection` in `prisma.config.ts`. |
 | `CONFIG.MISSING_EXTENSION_PACKS` | `contract emit` (e.g. contract uses `pgvector.Vector(...)` but config does not list the pgvector descriptor) | Add the descriptors named in `meta.missingExtensionPacks` to `extensions` in `prisma.config.ts`. See `references/contract.md`. |
-| `MIGRATION.PLANNING_FAILED` | `db init`, `db update` | Inspect `meta.conflicts`. Recovery is per-conflict — chain to `references/migrations.md`. |
+| `MIGRATION.PLANNING_FAILED` | `db init`, `db update`, `migration plan` | Inspect `meta.conflicts`. Recovery is per-conflict — chain to `references/migrations.md`. When `migration plan` raises it because the planner produced no operations, the conflict's `why` gives the next step (`migration new --from <hash>`, or `db sign` for a database managed with `db update`). |
 | `CLI.INIT_MISSING_FLAGS` / `CLI.INIT_INVALID_FLAG_VALUE` / `CLI.INIT_REINIT_NEEDS_FORCE` / `CLI.INIT_*` | `prisma orm init` | Re-run with the flags listed in `meta.missingFlags` or `meta.allowed`; a re-init needs `--confirm <directory name>`. `CLI.INIT_INSTALL_FAILED` (exit 4) and `CLI.INIT_EMIT_FAILED` (exit 5) are findings on a completed scaffold — the files are on disk; fix and re-run the named step. |
 | `MIGRATION.UNFILLED_PLACEHOLDER` | `node migrations/app/<dir>/migration.ts` (self-emit) or `db migrate` | Edit `migration.ts`, replace the `placeholder("<slot>")` named by `meta.slot` with a real query closure, self-emit. See `references/migrations.md`. |
 | `MIGRATION.FILE_MISSING` | Reading a migration package | Restore from version control or scaffold a fresh package with `migration plan` / `migration new`. |