@prisma/orm-sqlite 8.0.0-rc.12-dev.12 → 8.0.0-rc.12-dev.14

package/package.json

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

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

@@ -44,6 +44,7 @@ Both files are **emitted artefacts**. Edit the source; never the JSON or `.d.ts`
 - **Contract source.** A file the framework reads and lowers to the canonical Contract IR. Two flavours, both first-class:
   - **`contract.prisma` (PSL)** — schema-flavoured DSL. Canonical for typical apps and brownfield Prisma users. Wired by `contract: './<path>/contract.prisma'` — the target config (`ormConfig`, below) detects the `.prisma` extension and routes through the PSL provider. The first line of every `.prisma` file is `// use prisma-8`; `orm init` and `contract infer` write it, and the language server only serves diagnostics, completion, and formatting on files that carry it (it still recognises the header earlier releases wrote and rewrites it on Format).
   - **`contract.ts` (TypeScript builder)** — programmatic authoring with `defineContract({...}, ({ field, model, rel, type }) => ({...}))` from `@internal/postgres/contract-builder` (or `@internal/mongo/contract-builder`). Wired by `contract: './<path>/contract.ts'` — the façade detects the `.ts` extension and routes through the TS provider. Use when you need programmatic composition (per-tenant variants, generated fields) or constructs PSL doesn't yet express (e.g. registering a parameterised extension type — see pgvector's contract).
+  - **An existing Prisma schema, during adoption.** A project that still runs an earlier Prisma can point `contract:` at its current `schema.prisma` instead of writing a Prisma 8 contract: `contract: prisma6Schema('prisma/schema.prisma')` from `@internal/mongo/config` reads a Prisma 6 MongoDB schema, and `prisma7Schema` from `@internal/postgres/config` reads a Prisma 7 Postgres schema. The earlier Prisma keeps owning the database; after each change there, run `contract emit` and `db sign`. A construct Prisma 8 cannot express fails `contract emit` with a `PSL.PRISMA6_MONGO_*` or `PSL.PRISMA7_*` diagnostic. See the façade READMEs for the details.
 - **`prisma.config.ts`.** Wires the contract source, the database connection, the migrations directory, and any installed extensions. The file is an *envelope*: the unified CLI's `definePrismaConfig({...})` from `@prisma/cli-engine` wraps an `orm:` section built by the target's `defineConfig` — conventionally imported as `ormConfig` from `@internal/postgres/config` (or `@internal/mongo/config`). There is no flat form; a bare `defineConfig({ contract, ... })` default export fails with `CONFIG.VERSION_MARKER_MISSING`.
 
   ```typescript

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

@@ -289,7 +289,7 @@ Switch authoring later by re-running `prisma orm init` in the same directory. Th
 
 ## What Prisma 8 doesn't do yet
 
-- **Migration from another ORM.** Prisma 8 doesn't migrate your schema *from* Drizzle / Prisma 6/7 / Sequelize / TypeORM / Kysely / Knex / a raw driver. Workaround: install the matching `@internal/migrate-from-<orm>-skill` if one exists for your source, or treat the source as a brownfield database and `contract infer` from it. If you need a guided migration flow built-in, file a feature request via the `references/feedback.md` skill.
+- **Migration from another ORM.** Prisma 8 doesn't migrate your schema *from* Drizzle / Sequelize / TypeORM / Kysely / Knex / a raw driver. A Prisma 6 MongoDB schema and a Prisma 7 Postgres schema are the exception: they can be the contract source as they are (`prisma6Schema` / `prisma7Schema`, see `references/contract.md`). For the others: install the matching `@internal/migrate-from-<orm>-skill` if one exists for your source, or treat the source as a brownfield database and `contract infer` from it. If you need a guided migration flow built-in, file a feature request via the `references/feedback.md` skill.
 - **`prisma db push`-style production sync.** `db update` is the quick development path; for production, use migrations (`migration plan` + `db migrate`). PN deliberately does not offer a "push-to-prod-without-a-migration" surface — see `references/migrations.md`.
 - **Studio / GUI database browser.** Use `prisma db schema` for a CLI tree-style summary of the live DB. If you need an interactive UI, file a feature request via the `references/feedback.md` skill.