@prisma/orm-mongo 8.0.0-rc.5-dev.3 → 8.0.0-rc.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/orm-mongo",
-  "version": "8.0.0-rc.5-dev.3",
+  "version": "8.0.0-rc.6",
   "license": "Apache-2.0",
   "type": "module",
   "sideEffects": false,
@@ -10,16 +10,16 @@
     "skills"
   ],
   "dependencies": {
-    "@prisma/orm-family-mongo": "8.0.0-rc.5-dev.3",
-    "@prisma/orm-framework": "8.0.0-rc.5-dev.3",
-    "@prisma/orm-target-mongo": "8.0.0-rc.5-dev.3",
-    "@prisma/orm-toolchain": "8.0.0-rc.5-dev.3",
+    "@prisma/orm-family-mongo": "8.0.0-rc.6",
+    "@prisma/orm-framework": "8.0.0-rc.6",
+    "@prisma/orm-target-mongo": "8.0.0-rc.6",
+    "@prisma/orm-toolchain": "8.0.0-rc.6",
     "pathe": "^2.0.3"
   },
   "devDependencies": {
-    "@internal/mongo": "8.0.0-rc.5-dev.3",
-    "@repo/tsconfig": "8.0.0-rc.5-dev.3",
-    "@repo/tsdown": "8.0.0-rc.5-dev.3",
+    "@internal/mongo": "8.0.0-rc.6",
+    "@repo/tsconfig": "8.0.0-rc.6",
+    "@repo/tsdown": "8.0.0-rc.6",
     "tsdown": "0.22.14",
     "typescript": "5.9.3"
   },

package/skills/prisma-8/SKILL.md

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

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

@@ -105,40 +105,32 @@ changes:
       regex:
         - "(Date|Timestamp|Timestamptz|Time)(\\([0-9]+\\))?\\s+@default\\(\""
       anyMatch: true
-
+  - id: orm-init-no-longer-installs-agent-skills
+    summary: |
+      `prisma orm init` no longer installs agent skills: the GitHub fetch (`npx skills add`)
+      is removed and nothing inside `orm init` replaces it. Agent-skills setup belongs to the
+      family-level `prisma init` command. The `--skip-skills` flag is removed with the
+      behavior it opted out of. Existing projects keep whatever skills they already have;
+      only scripts that invoke `orm init` and expect it to deliver skills (or pass
+      `--skip-skills`) need to change.
+    detection:
+      glob: "**/*.{sh,yml,yaml,json,md}"
+      regex:
+        - '\borm\s+init\b'
+      anyMatch: true
+  - id: contract-artifacts-restamp
+    summary: |
+      The emitted `contract.json` / `contract.d.ts` embed the toolchain version, which moves
+      to 8.0.0-rc.6. Run `contract emit` once after upgrading so the emitted artifacts match
+      the installed toolchain. The restamp is independent of the other changes in this
+      release.
+    detection:
+      glob: "**/contract.json"
+      contains:
+        - '"version": "8.0.0-rc.5"'
 ---
 
-# 8.0.0-rc.4 → 8.0.0-rc.5 — User upgrade instructions
-
-## `attach-pg-client-error-listener`
-
-Walk every file matched by `detection.glob`. For each `pg.Client` or `pg.Pool` your code constructs and uses directly (not one handed to `postgres({ pg: ... })` / `supabase({ pg: ... })` — the runtime covers those since rc.5), attach an `'error'` listener right after construction, before `connect()`:
-
-```ts
-const client = new pg.Client({ connectionString });
-client.on('error', () => {});
-await client.connect();
-```
-
-A no-op listener is enough: connect and query failures still reject their own promises, so nothing real is masked — the listener only stops a dropped idle connection from becoming an uncaught exception. If the handle is long-lived and you have a logging channel, log the error instead of discarding it.
-
-Note that a surrounding `try/catch` does **not** cover this case — the `'error'` event is emitted on the client object asynchronously, outside any promise chain the `catch` can see.
-
-# 8.0.0-rc.4 → 8.0.0-rc.5 — User upgrade instructions
-
-## `attach-pg-client-error-listener`
-
-Walk every file matched by `detection.glob`. For each `pg.Client` or `pg.Pool` your code constructs and uses directly (not one handed to `postgres({ pg: ... })` / `supabase({ pg: ... })` — the runtime covers those since rc.5), attach an `'error'` listener right after construction, before `connect()`:
-
-```ts
-const client = new pg.Client({ connectionString });
-client.on('error', () => {});
-await client.connect();
-```
-
-A no-op listener is enough: connect and query failures still reject their own promises, so nothing real is masked — the listener only stops a dropped idle connection from becoming an uncaught exception. If the handle is long-lived and you have a logging channel, log the error instead of discarding it.
-
-Note that a surrounding `try/catch` does **not** cover this case — the `'error'` event is emitted on the client object asynchronously, outside any promise chain the `catch` can see.
+# 8.0.0-rc.5 → 8.0.0-rc.6 — User upgrade instructions
 
 # PostgreSQL temporal representations
 
@@ -153,4 +145,13 @@ naming the `*String` type that reads the same column losslessly. And a nested re
 text a flat read does, because temporal expressions are cast to `text` before PostgreSQL builds the
 JSON, which means both reflect the session `TimeZone`.
 
+## `orm-init-no-longer-installs-agent-skills`
+
+Nothing to change in an existing project: skills already on disk stay as they are. Walk every `orm init` invocation the detection finds (a mention in prose that is not a command needs no action):
+
+- An invocation passing `--skip-skills`: drop the flag — it no longer exists and the invocation fails with an unknown-flag error. The behavior it opted out of is gone, so the flagless invocation is the equivalent.
+- A plain invocation with no flag: the scaffold itself is unchanged, but it no longer installs agent skills. If the script (or the person following it) relied on that, run `prisma init` in the project afterwards; that command owns skills setup now. If skills were incidental, no change is needed.
+
+## `contract-artifacts-restamp`
 
+For every `contract.json` matched by `detection`, run the project's emit command (`prisma contract emit`, or the project's `contract:emit` script) once after upgrading. The only expected diff is the embedded `version` moving to `8.0.0-rc.6`.

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

@@ -69,112 +69,20 @@ changes:
       regex:
         - "pg/(date|timestamp|timestamptz|time)-temporal@1"
       anyMatch: true
-
+  - id: contract-space-restamp
+    summary: |
+      The emitted contract artifacts embed the toolchain version, which moves to 8.0.0-rc.6.
+      Rebuild the extension's contract space (the package's `build:contract-space` script)
+      once after upgrading so the emitted artifacts match the installed toolchain. The
+      toolchain also re-released against `@prisma/cli-engine@0.2.2` (a CLI-side fix with no
+      extension-facing surface).
+    detection:
+      glob: "**/contract.json"
+      contains:
+        - '"version": "8.0.0-rc.5"'
 ---
 
-# 8.0.0-rc.4 → 8.0.0-rc.5 — Extension author upgrade instructions
-
-## `wrap-pg-constructions-with-suppress-idle-connection-errors`
-
-Walk every file matched by `detection.glob`. For each pg `Pool` or `Client` the extension constructs, wrap the construction:
-
-```ts
-import { suppressIdleConnectionErrors } from '@internal/driver-postgres/runtime';
-
-const pool = suppressIdleConnectionErrors(
-  new Pool({ connectionString: options.url }),
-);
-```
-
-This is the same translation applied to the in-repo `@internal/postgres` and `@internal/extension-supabase` runtimes in this transition. The helper only attaches a no-op `'error'` listener (connect/query failures still reject their own promises), so behavior is otherwise unchanged; without it, a dropped idle connection crashes the process that hosts the extension.
-
-If your extension's test suite fakes the `pg` module, the fakes need an `on` method (`on = vi.fn().mockReturnThis()` on a class fake, or `on: vi.fn()` on an object literal) — the runtime now calls `.on('error', ...)` on every pool, client, and checked-out pool client.
-## `distinct-on-requires-postgres-capability`
-
-`Collection#distinctOn(...)` used to compile and run on any target, but only Postgres ever
-rendered its `DISTINCT ON` clause — a call on any other target (SQLite) compiled clean and
-silently returned undeduped rows at runtime. The method now carries the same capability gate the
-sql-builder lane already enforces: its parameter type narrows to `never` unless the contract
-declares `postgres.distinctOn`, so the same call is a compile error on a contract that lacks it,
-and a runtime error carrying `ORM.CAPABILITY_MISSING` if reached dynamically (e.g. through a
-hand-built `CollectionState`).
-
-Find every `.distinctOn(...)` call your code makes on a `Collection` and check whether the
-contract it runs against declares `postgres.distinctOn`. If it does, nothing changes — the call
-already worked correctly and keeps compiling. If it does not, the call was already producing the
-wrong result set; either move the collection onto a Postgres-capable contract, or remove the
-`.distinctOn(...)` call and accept the undeduped rows it was silently returning before.
-
-`Collection#distinct(...)` is unaffected — it lowers to a portable `ROW_NUMBER` dedup and needs
-no capability, on any target.
-
-## `groupby-pre-group-pagination-now-scopes-rows`
-
-Any `.take(...)`, `.skip(...)`, `.cursor(...)`, `.distinct(...)`, `.distinctOn(...)`, or
-`.orderBy(...)` your extension calls *before* `.groupBy(...)` on a `Collection` used to be
-silently dropped once `.groupBy(...)` joined the chain — the aggregate reduced over every
-matching row, ignoring the pagination clause entirely. It now scopes the rows that get grouped,
-the same way root `.aggregate()` scopes its rows (see the sibling entry for that fix, already
-shipped in `8.0.0-rc.4` → `8.0.0-rc.5`'s predecessor window).
-
-There is no detection regex for this one worth writing: the call sites that need re-checking
-look identical, in source, to the call sites that already worked correctly (a chain built with
-this scoping in mind, versus one that assumed the pagination clause was a no-op). Grep for
-`.groupBy(` and read every match with a pre-group pagination clause; if the test asserting its
-result seeds fewer distinct groups than pagination scope allows, or asserts totals computed over
-every row rather than the paginated window, the expected values need updating to match the now-
-correct behavior.
-
-## `groupby-post-group-pagination-requires-order-by`
-
-`GroupedCollection` (what `.groupBy(...)` returns) gained `take()`, `skip()`, and `orderBy()`,
-which page the *grouped* rows when written after `.groupBy(...)` — previously `.groupBy(...)` had
-no chain of its own past `.having(...)`. Calling post-group `take()` or `skip()` without a prior
-post-group `orderBy()` is a compile error: the parameter type narrows to `never`, because a
-database may return groups in any order and "the first n groups" has no defined meaning without
-one.
-
-If your extension's own code (or its test suite) calls `.groupBy(...).take(...)` or
-`.groupBy(...).skip(...)` with no `.orderBy(...)` between them, it will fail to compile after this
-upgrade. There is no default ordering to insert automatically — add an `.orderBy(...)` naming one
-of the fields you passed to `groupBy(...)` (ascending or descending is your call; whichever
-matches what "the first n groups" should mean for that query) before the `take()` / `skip()` call.
-
-# 8.0.0-rc.4 → 8.0.0-rc.5 — Extension author upgrade instructions
-
-## `wrap-pg-constructions-with-suppress-idle-connection-errors`
-
-Walk every file matched by `detection.glob`. For each pg `Pool` or `Client` the extension constructs, wrap the construction:
-
-```ts
-import { suppressIdleConnectionErrors } from '@internal/driver-postgres/runtime';
-
-const pool = suppressIdleConnectionErrors(
-  new Pool({ connectionString: options.url }),
-);
-```
-
-This is the same translation applied to the in-repo `@internal/postgres` and `@internal/extension-supabase` runtimes in this transition. The helper only attaches a no-op `'error'` listener (connect/query failures still reject their own promises), so behavior is otherwise unchanged; without it, a dropped idle connection crashes the process that hosts the extension.
-
-If your extension's test suite fakes the `pg` module, the fakes need an `on` method (`on = vi.fn().mockReturnThis()` on a class fake, or `on: vi.fn()` on an object literal) — the runtime now calls `.on('error', ...)` on every pool, client, and checked-out pool client.
-## `distinct-on-requires-postgres-capability`
-
-`Collection#distinctOn(...)` used to compile and run on any target, but only Postgres ever
-rendered its `DISTINCT ON` clause — a call on any other target (SQLite) compiled clean and
-silently returned undeduped rows at runtime. The method now carries the same capability gate the
-sql-builder lane already enforces: its parameter type narrows to `never` unless the contract
-declares `postgres.distinctOn`, so the same call is a compile error on a contract that lacks it,
-and a runtime error carrying `ORM.CAPABILITY_MISSING` if reached dynamically (e.g. through a
-hand-built `CollectionState`).
-
-Find every `.distinctOn(...)` call your code makes on a `Collection` and check whether the
-contract it runs against declares `postgres.distinctOn`. If it does, nothing changes — the call
-already worked correctly and keeps compiling. If it does not, the call was already producing the
-wrong result set; either move the collection onto a Postgres-capable contract, or remove the
-`.distinctOn(...)` call and accept the undeduped rows it was silently returning before.
-
-`Collection#distinct(...)` is unaffected — it lowers to a portable `ROW_NUMBER` dedup and needs
-no capability, on any target.
+# 8.0.0-rc.5 → 8.0.0-rc.6 — Extension author upgrade instructions
 
 # PostgreSQL temporal representations, for extension authors
 
@@ -189,4 +97,6 @@ that reads them losslessly. The driver hands temporal OIDs through as server tex
 building a `Date`. And temporal expressions are cast to `text` before PostgreSQL builds JSON, so a
 nested read returns the same text a flat one does.
 
+## `contract-space-restamp`
 
+For every `contract.json` matched by `detection`, run the extension package's `build:contract-space` script (or its emit command) once after upgrading. Beyond the temporal changes above, the only expected diff is the embedded `version` moving to `8.0.0-rc.6`. The toolchain also re-released against `@prisma/cli-engine@0.2.2`; that change has no extension-facing surface.