prisma 8.0.0-rc.19-dev.138 → 8.0.0-rc.20-dev.139

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prisma",
-  "version": "8.0.0-rc.19-dev.138",
+  "version": "8.0.0-rc.20-dev.139",
   "description": "The Prisma CLI: one binary for the ORM, Composer, and the Prisma Developer Platform.",
   "type": "module",
   "bin": {
@@ -45,10 +45,10 @@
   "dependencies": {
     "@manypkg/tools": "^2.1.2",
     "@prisma/cli-engine": "0.6.2",
-    "@prisma/composer-cli": "0.25.0-dev.5",
+    "@prisma/composer-cli": "0.26.0-dev.2",
     "@prisma/compute-sdk": "0.43.0",
     "@prisma/management-api-sdk": "1.80.0",
-    "@prisma/orm-toolchain": "8.0.0-rc.14-dev.20",
+    "@prisma/orm-toolchain": "8.0.0-rc.14-dev.24",
     "@vercel/detect-agent": "^1.2.3",
     "better-result": "^2.9.2",
     "cross-spawn": "^7.0.6",
@@ -57,10 +57,10 @@
     "open": "^11.0.0"
   },
   "devDependencies": {
-    "@prisma/cli": "8.0.0-rc.19-dev.138",
+    "@prisma/cli": "8.0.0-rc.20-dev.139",
     "@prisma/credentials-store": "^7.8.0",
-    "@repo/cli-telemetry": "8.0.0-rc.19-dev.138",
-    "@repo/tsconfig": "8.0.0-rc.19-dev.138",
+    "@repo/cli-telemetry": "8.0.0-rc.20-dev.139",
+    "@repo/tsconfig": "8.0.0-rc.20-dev.139",
     "@types/node": "^22.19.19",
     "tsdown": "^0.21.10",
     "typescript": "^6.0.3",

package/skills/prisma-platform-core-concepts/SKILL.md

@@ -2,7 +2,7 @@
 name: prisma-platform-core-concepts
 metadata:
   library: "prisma"
-  library_version: "8.0.0-rc.19-dev.138"
+  library_version: "8.0.0-rc.20-dev.139"
   version: 2026.9.2
 description: >-
   Use when hosting, deploying, or operating an app on the Prisma Platform:
@@ -71,26 +71,42 @@ packages (`prisma-composer-core-concepts` in `@prisma/composer`,
 `prisma-orm-core-concepts` in `@prisma/orm-postgres`), so they appear after
 this install plus `prisma skills sync`, not before.
 
-Two config files with different owners:
-
-1. `prisma.config.ts` configures the CLI. Each top-level key is a section
-   owned by one product, and this CLI recognises exactly three: `orm`,
-   `composer`, and `skills`. The composed shape:
-
-   ```ts
-   import { definePrismaConfig } from "prisma/config";
-   import { defineConfig } from "@prisma/orm-postgres/config";
-
-   export default definePrismaConfig({
-     orm: defineConfig({ contract: "./src/prisma/contract.prisma" }),
-     skills: { agents: ["claude"] },
-   });
-   ```
+One config file, `prisma.config.ts`, configures the CLI and every product
+it runs. Each top-level key is a section owned by one product, and this CLI
+recognises exactly three: `orm`, `composer`, and `skills`. The composed
+shape:
+
+```ts
+import { definePrismaConfig } from "prisma/config";
+import { defineConfig as composer } from "@prisma/composer/config";
+import { nodeBuild } from "@prisma/composer/node/control";
+import {
+  prismaCloud,
+  prismaState,
+} from "@prisma/composer-prisma-cloud/control";
+import { defineConfig as orm } from "@prisma/orm-postgres/config";
+
+export default definePrismaConfig({
+  composer: composer({
+    extensions: [prismaCloud(), nodeBuild()],
+    state: prismaState(),
+  }),
+  orm: orm({ contract: "./src/prisma/contract.prisma" }),
+  skills: { agents: ["claude"] },
+});
+```
 
-2. `prisma-composer.config.ts` configures Composer itself and is a separate,
-   mandatory file for `dev` and `deploy`: without it `dev` fails with
-   `CONFIG.FILE_MISSING`. Its contents belong to
-   `prisma-composer-core-concepts`.
+`dev` and `deploy` read the `composer` section and nothing else; what goes
+in it belongs to `prisma-composer-core-concepts`. A separate
+`prisma-composer.config.ts` is no longer read, and the old setup is refused,
+never silently ignored: `CONFIG.SECTION_MISSING` when no loaded
+`prisma.config.ts` declares a `composer` section, `CONFIG.FIELD_RETIRED`
+when the section still has `configPath`, and `CONFIG.FILE_RETIRED` when a
+`prisma-composer.config.*` sits next to the declaring `prisma.config.ts`.
+All three arrive under the CLI's `CLI.CONFIG_SECTION_INVALID`. For
+`CONFIG.SECTION_MISSING`, write the section. For the other two, move the
+old file's `extensions` and `state` into the section, then delete the
+`configPath` field or the old file.
 
 ## The resource model