@prisma/orm-postgres 8.0.0-rc.8-dev.1 → 8.0.0-rc.8-dev.3

package/README.md

@@ -50,7 +50,3 @@ An application that outgrows the default wiring installs the four platform packa
 ## Responsibilities
 
 Composition only. Every behavior it exposes lives in the platform packages; this package chooses the default combination of them and gives it one name.
-
-## Dependencies
-
-`@prisma/orm-framework`, `@prisma/orm-family-sql`, `@prisma/orm-target-postgres`, and `@prisma/orm-toolchain` at exact lockstep versions, plus `pg` and `pathe`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/orm-postgres",
-  "version": "8.0.0-rc.8-dev.1",
+  "version": "8.0.0-rc.8-dev.3",
   "license": "Apache-2.0",
   "type": "module",
   "sideEffects": false,
@@ -10,19 +10,19 @@
     "skills"
   ],
   "dependencies": {
-    "@prisma/orm-family-sql": "8.0.0-rc.8-dev.1",
-    "@prisma/orm-framework": "8.0.0-rc.8-dev.1",
-    "@prisma/orm-target-postgres": "8.0.0-rc.8-dev.1",
-    "@prisma/orm-toolchain": "8.0.0-rc.8-dev.1",
+    "@prisma/orm-family-sql": "8.0.0-rc.8-dev.3",
+    "@prisma/orm-framework": "8.0.0-rc.8-dev.3",
+    "@prisma/orm-target-postgres": "8.0.0-rc.8-dev.3",
+    "@prisma/orm-toolchain": "8.0.0-rc.8-dev.3",
     "@types/pg": "8.20.4",
     "pathe": "^2.0.3",
     "pg": "8.22.0"
   },
   "devDependencies": {
-    "@internal/postgres": "8.0.0-rc.8-dev.1",
-    "@repo/tsconfig": "8.0.0-rc.8-dev.1",
-    "@internal/publish-surface": "8.0.0-rc.8-dev.1",
-    "@repo/tsdown": "8.0.0-rc.8-dev.1",
+    "@internal/postgres": "8.0.0-rc.8-dev.3",
+    "@repo/tsconfig": "8.0.0-rc.8-dev.3",
+    "@internal/publish-surface": "8.0.0-rc.8-dev.3",
+    "@repo/tsdown": "8.0.0-rc.8-dev.3",
     "tsdown": "0.22.14",
     "typescript": "5.9.3",
     "vitest": "5.0.0-rc.2"
@@ -179,7 +179,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/prisma/prisma.git",
+    "url": "https://github.com/prisma/orm.git",
     "directory": "packages/9-public/@prisma/orm-postgres"
   },
   "scripts": {

package/skills/prisma-8/SKILL.md

@@ -17,7 +17,7 @@ description: >-
   (schema.prisma + @prisma/client projects).
 metadata:
   library: '@prisma/orm-postgres'
-  library_version: '8.0.0-rc.8-dev.1'
+  library_version: '8.0.0-rc.8-dev.3'
 ---
 
 # Prisma Next (Prisma 8)

package/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.8-to-8.0.0-rc.9/instructions.md

@@ -0,0 +1,29 @@
+---
+from: "8.0.0-rc.8"
+to: "8.0.0-rc.9"
+changes:
+  - id: mongo-index-projections-use-native-lists
+    summary: |
+      MongoDB wildcard index `include` and `exclude` projections in Prisma schema files must use native PSL lists instead of encoded list strings.
+    detection:
+      glob: "**/*.prisma"
+      matches:
+        - '\b(?:include|exclude)\s*:\s*"\[[^"\r\n]*\]"'
+  - id: mongo-text-index-weights-use-native-records
+    summary: |
+      MongoDB text-index `weights` in Prisma schema files must use native PSL records instead of encoded JSON strings.
+    detection:
+      glob: "**/*.prisma"
+      matches:
+        - '\bweights\s*:\s*"\{\s*(?:\\.|[^"\\])*\}"'
+---
+
+# 8.0.0-rc.8 → 8.0.0-rc.9 — User upgrade instructions
+
+## `mongo-index-projections-use-native-lists`
+
+For every Prisma schema matched by `detection`, replace encoded projection strings with native PSL lists. For example, change `include: "[a, b]"` to `include: ["a", "b"]` and `exclude: "[a]"` to `exclude: ["a"]`. Decode each string's fields in their existing order and preserve whether the argument is `include` or `exclude`.
+
+## `mongo-text-index-weights-use-native-records`
+
+For every Prisma schema matched by `detection`, replace the encoded JSON string passed to `weights` with a native PSL record. For example, change `weights: "{\"title\": 10}"` to `weights: { title: 10 }`, preserving every field name and numeric weight.

package/skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.8-to-8.0.0-rc.9/instructions.md

@@ -0,0 +1,14 @@
+---
+from: "8.0.0-rc.8"
+to: "8.0.0-rc.9"
+changes:
+  - id: remove-nested-relations-from-sql-orm-upsert-and-batch-create
+    summary: |
+      SQL ORM `upsert({ create })`, `createAll()`, and `createAndCount()` payloads no longer accept nested relation mutation callbacks, which these operations cannot execute. Remove the callbacks and create related records separately, or use ordinary `create()` when the records must be created as one nested relation operation.
+---
+
+# 8.0.0-rc.8 → 8.0.0-rc.9 — Extension author upgrade instructions
+
+## `remove-nested-relations-from-sql-orm-upsert-and-batch-create`
+
+Find SQL ORM calls to `upsert()`, `createAll()`, and `createAndCount()` whose create payloads contain relation fields assigned callback functions. Remove those callbacks and create the related records separately. When the operation requires nested relation creation, replace it with ordinary `create()`, which continues to accept and execute relation mutation callbacks.