@prisma/orm-mongo 8.0.0-rc.9-dev.9 → 8.0.0-rc.9-dev.10

package/package.json

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

package/skills/prisma-8/SKILL.md

@@ -18,7 +18,7 @@ description: >-
   (schema.prisma + @prisma/client projects).
 metadata:
   library: '@prisma/orm-mongo'
-  library_version: '8.0.0-rc.9-dev.9'
+  library_version: '8.0.0-rc.9-dev.10'
 ---
 
 # Prisma 8 (Prisma 8)

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

@@ -67,7 +67,7 @@ Set `logLevel: 'debug'` only while troubleshooting; default `'info'` in committe
 ### 4. Verify the dev loop
 
 1. Start `vite dev`.
-2. Watch for the success log: `[prisma-next] emitted contract.d.ts + contract.json`.
+2. Watch for the success log: `[prisma] emitted contract.d.ts + contract.json`.
 3. Edit `prisma/schema.psl` (e.g. add a field to a model).
 4. Within ~150ms (the debounce), watch for a re-emit log line.
 5. Type-check your application code that uses the new field — should pass without restarting the dev server.

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

@@ -9,12 +9,12 @@ The skill's job is to pick the *right channel* — GitHub issue or Discord — a
 
 Canonical channels:
 
-- **GitHub Issues** (bugs + concrete feature requests): <https://github.com/prisma/prisma-next/issues/new/choose>
+- **GitHub Issues** (bugs + concrete feature requests): <https://github.com/prisma/orm/issues/new/choose>
 - **Prisma Discord** (Q&A, design feedback, direct team contact — including extension authors): <https://pris.ly/discord>
 
 ## When to Use
 
-- A capability-gap entry from another `prisma-next-*` skill fired and the user said *"yes, file the feature request"*.
+- A capability-gap entry from another `prisma-8` skill fired and the user said *"yes, file the feature request"*.
 - User says *"this is a bug"*, *"file this"*, *"report this"*, *"file an issue against PN"*, *"send feedback"*, *"this should be a feature"*.
 - User describes an unexpected behaviour — wrong exit code, error message that didn't match what happened, type signature that doesn't match runtime behaviour, planner refused a migration that looked safe — and wants it on the framework team's radar.
 - User asks *"can I ask the Prisma team about this?"*, *"is there somewhere I can talk to the team?"*, *"is this the intended way to do X?"*, *"how should I integrate <my extension / my tool> with PN?"*, or any other open-ended Q&A or design-feedback prompt — including extension authors asking integration questions.
@@ -42,7 +42,7 @@ The user wants to hand something off to the team. Which channel?
 
 - The user describes a concrete bug (see *Classify* below for the bug-vs-feature split).
 - The user has a concrete feature request — a named capability, a specific API shape, a specific CLI flag — that they want on the backlog.
-- A capability-gap entry from another `prisma-next-*` skill routed them here for a feature request.
+- A capability-gap entry from another `prisma-8` skill routed them here for a feature request.
 
 **Prisma Discord** (<https://pris.ly/discord>) if any of:
 
@@ -103,7 +103,7 @@ For **feature requests**, additionally:
 
 ### 4. Render the body
 
-The repository ships GitHub Issue Forms (`.github/ISSUE_TEMPLATE/bug_report.yml` and `feature_request.yml`). When the user lands on <https://github.com/prisma/prisma-next/issues/new/choose> they pick the matching template and fill in the form fields; the skill produces the body in the same structured shape so it maps onto the form one-to-one (and so `gh issue create --body-file` produces a parseable artifact even when the form isn't in play).
+The repository ships GitHub Issue Forms (`.github/ISSUE_TEMPLATE/bug_report.yml` and `feature_request.yml`). When the user lands on <https://github.com/prisma/orm/issues/new/choose> they pick the matching template and fill in the form fields; the skill produces the body in the same structured shape so it maps onto the form one-to-one (and so `gh issue create --body-file` produces a parseable artifact even when the form isn't in play).
 
 Bug-report body shape (fields named to match `.github/ISSUE_TEMPLATE/bug_report.yml`):
 
@@ -195,7 +195,7 @@ Preferred. Two steps:
 If `gh` is not installed: open the prefilled new-issue URL in the browser:
 
 ~~~text
-https://github.com/prisma/prisma-next/issues/new/choose
+https://github.com/prisma/orm/issues/new/choose
 ~~~
 
 …and instruct the user to paste the rendered body. The agent can copy the body to the clipboard via `pbcopy` (macOS), `xclip` (Linux), or by simply printing it in the chat for the user to copy.
@@ -205,7 +205,7 @@ https://github.com/prisma/prisma-next/issues/new/choose
 When step 1 picked the Discord channel (steps 2–7 do not apply):
 
 1. **Surface the link.** Give the user the canonical invite: <https://pris.ly/discord>. Suggest the channel that fits the question:
-   - General usage / Q&A → the public `#help` or `#prisma-next` channel (channel naming evolves; the invite landing page lists current channels).
+   - General usage / Q&A → the public `#help` channel (the invite landing page lists current channels).
    - Extension-author / partner-integration / breaking-change-coordination questions → the public extension-authors channel, or the user can ping a maintainer directly once they're in the server.
 2. **Help draft the opening message.** Prisma's Discord is searchable; a well-framed opening message gets a faster, more useful answer. The agent drafts a short message with:
    - One-sentence summary of what the user is trying to do.
@@ -231,11 +231,11 @@ When step 1 picked the Discord channel (steps 2–7 do not apply):
 
 ## What Prisma 8 doesn't do yet
 
-- **In-product feedback channel.** No `prisma-next feedback` CLI command. The GitHub Issues page is the canonical surface. If you want a CLI-side feedback command, file a feature request via this skill.
+- **In-product feedback channel.** No `prisma feedback` CLI command. The GitHub Issues page is the canonical surface. If you want a CLI-side feedback command, file a feature request via this skill.
 
 ## Reference Files
 
-- <https://github.com/prisma/prisma-next/issues/new/choose> — the canonical submission surface.
+- <https://github.com/prisma/orm/issues/new/choose> — the canonical submission surface.
 - <https://cli.github.com/manual/gh_issue_create> — the `gh` command reference.
 
 ## Checklist

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

@@ -520,7 +520,7 @@ Objects whose `@@control` policy excludes them from Prisma 8's managed surface a
 
 ## Telemetry
 
-The CLI collects anonymous usage data by default. To opt out, set `PRISMA_NEXT_DISABLE_TELEMETRY=1` or `DO_NOT_TRACK=1` in your environment. See [`docs/Telemetry.md`](../../docs/Telemetry.md) for the full opt-out reference.
+The CLI collects anonymous usage data by default. To opt out, set `PRISMA_DISABLE_TELEMETRY=1` or `DO_NOT_TRACK=1` in your environment. See [`docs/Telemetry.md`](../../docs/Telemetry.md) for the full opt-out reference.
 
 ## Checklist
 

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

@@ -182,7 +182,7 @@ pnpm dlx prisma@latest orm init                          # interactive
 pnpm dlx prisma@latest orm init --yes --target postgres --authoring psl
 ```
 
-> **Telemetry is opt-out.** The CLI collects anonymous usage data by default. Every command — including `init` — prints a one-time notice to **stderr** on first use, then sends; there is no interactive consent prompt. Opt out anytime by running `prisma telemetry disable`, or with `DO_NOT_TRACK=1` or `PRISMA_NEXT_DISABLE_TELEMETRY=1`. The command stores `"enableTelemetry": false` in your user config for you (the CLI's per-user config dir, **not** `prisma.config.ts`). Run `prisma telemetry status` to see what's currently in effect. This is relevant for agent-driven runs — the CLI records that an agent invoked it. What's collected, the per-user config path, and how to fully reset are documented in `docs/Telemetry.md`.
+> **Telemetry is opt-out.** The CLI collects anonymous usage data by default. Every command — including `init` — prints a one-time notice to **stderr** on first use, then sends; there is no interactive consent prompt. Opt out anytime by running `prisma telemetry disable`, or with `DO_NOT_TRACK=1` or `PRISMA_DISABLE_TELEMETRY=1`. The command stores `"enableTelemetry": false` in your user config for you (the CLI's per-user config dir, **not** `prisma.config.ts`). Run `prisma telemetry status` to see what's currently in effect. This is relevant for agent-driven runs — the CLI records that an agent invoked it. What's collected, the per-user config path, and how to fully reset are documented in `docs/Telemetry.md`.
 
 The flags `init` accepts (run `prisma orm init --help` for the source of truth):
 
@@ -203,7 +203,7 @@ The flags `init` accepts (run `prisma orm init --help` for the source of truth):
 - `prisma.config.ts` at the project root (envelope form — see `references/contract.md`).
 - The contract source at `--schema-path` (`src/prisma/contract.prisma` by default).
 - `db.ts` in the same directory as the contract source.
-- `prisma-next.md` — a human quick-reference.
+- `prisma-8.md` — a human quick-reference.
 - `.env.example` (and `.env` if `--write-env`).
 - Updates `package.json` (deps + a `contract:emit` script) and `tsconfig.json` (required compiler options).
 - Installs deps and runs `prisma contract emit` once. If the install or the emit fails, the scaffold is still on disk and init exits `4` (`CLI.INIT_INSTALL_FAILED`) or `5` (`CLI.INIT_EMIT_FAILED`) with the step to re-run.

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

@@ -1,8 +1,37 @@
 ---
 from: "8.0.0-rc.9"
 to: "8.0.0-rc.10"
-# Prisma 8 naming sweep: prose only, no entry required
 changes:
+  - id: schema-header-use-prisma-8
+    summary: |
+      The schema header that marks a Prisma 8 schema is now `// use prisma-8`. The language server
+      still serves the old header and its Format action rewrites it; new schemas and the
+      inferred-schema printer write the new form. Replace `// use prisma-next`
+      at the top of every `.prisma` file.
+    detection:
+      glob: "**/*.prisma"
+      contains:
+        - "// use prisma-next"
+  - id: env-vars-drop-next-infix
+    summary: |
+      The CLI environment variables lost their `NEXT_` infix: `PRISMA_NEXT_DISABLE_TELEMETRY`,
+      `PRISMA_NEXT_TELEMETRY_ENDPOINT`, `PRISMA_NEXT_DEBUG`, and the rest are now
+      `PRISMA_DISABLE_TELEMETRY`, `PRISMA_TELEMETRY_ENDPOINT`, `PRISMA_DEBUG`, and so on. The old
+      `PRISMA_NEXT_DISABLE_TELEMETRY` opt-out is still honoured; the others are not. Rename them
+      in shell profiles, `.env` files, and CI configuration. The per-user telemetry config also moved
+      from `~/.config/prisma-next/` to `~/.config/prisma-8/`, so the consent prompt runs once more.
+    detection:
+      glob: "**/*"
+      contains:
+        - "PRISMA_NEXT_"
+  - id: primer-file-prisma-8-md
+    summary: |
+      The quick-reference primer `init` writes at the project root is now `prisma-8.md`. Rename the
+      existing `prisma-next.md` and update any README or agent instruction that points at it.
+    detection:
+      glob: "**/prisma-next.md"
+      contains:
+        - "#"
   - id: to-one-relations-record-nullable
     summary: |
       Every `1:1` and `N:1` relation in `contract.json` now carries a `nullable` boolean. A
@@ -28,3 +57,15 @@ For every `contract.json` matched by `detection`, run the project's emit command
 ## `contract-dts-exports-models`
 
 After the emit, `import type { Models, models } from './prisma/contract'` (the project's contract path) gives `Models.<namespace>_<Model>` for every model, and `Scalars<M>` / `Shape<M, { '+': 'relation' }>` from `@prisma/orm-postgres/family-contract/types` (or the Mongo family package) derive the default row and a data structure with relations from it. Replace hand-written row types that duplicate a model's fields with these when convenient.
+
+## `schema-header-use-prisma-8`
+
+For every `.prisma` file matched by `detection`, replace the first-line header `// use prisma-next` with `// use prisma-8`. Nothing else in the file changes.
+
+## `env-vars-drop-next-infix`
+
+For every file matched by `detection`, replace the `PRISMA_NEXT_` prefix with `PRISMA_` on each environment variable name. Delete `~/.config/prisma-next/` (or `%APPDATA%\prisma-next\` on Windows); the CLI recreates its config under `prisma-8` and asks for telemetry consent once.
+
+## `primer-file-prisma-8-md`
+
+Rename `prisma-next.md` at the project root to `prisma-8.md`, and update any link to it in the project README or agent instructions.

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

@@ -1,10 +1,30 @@
 ---
 from: "8.0.0-rc.9"
 to: "8.0.0-rc.10"
-# Prisma 8 naming sweep: prose only, no entry required
 # sql-orm-client doc-comment sweep: reviewed, no entry required
 # postgres shell dependency ownership: reviewed, no extension-author action required; bundled packages now declare the catalog Node/pg type dependencies that public shell manifests mirror
 changes:
+  - id: schema-header-use-prisma-8
+    summary: |
+      The schema header that marks a Prisma 8 schema is now `// use prisma-8`. The language server
+      still serves the old header and its Format action rewrites it; new schemas and the
+      inferred-schema printer write the new form. Replace `// use prisma-next`
+      at the top of every `.prisma` file the extension ships or tests against.
+    detection:
+      glob: "**/*.prisma"
+      contains:
+        - "// use prisma-next"
+  - id: env-vars-drop-next-infix
+    summary: |
+      The CLI environment variables lost their `NEXT_` infix: `PRISMA_NEXT_DISABLE_TELEMETRY`,
+      `PRISMA_NEXT_TELEMETRY_ENDPOINT`, `PRISMA_NEXT_DEBUG`, and the rest are now
+      `PRISMA_DISABLE_TELEMETRY`, `PRISMA_TELEMETRY_ENDPOINT`, `PRISMA_DEBUG`, and so on. The old
+      `PRISMA_NEXT_DISABLE_TELEMETRY` opt-out is still honoured; the others are not. Rename them
+      in the extension's test setup and CI configuration.
+    detection:
+      glob: "**/*"
+      contains:
+        - "PRISMA_NEXT_"
   - id: to-one-relations-record-nullable
     summary: |
       `ContractNonJunctionRelation`'s `'1:1'` and `'N:1'` members now require `nullable: boolean`,
@@ -33,3 +53,11 @@ For every TypeScript file matched by `detection`, find each object literal that
 ## `contract-space-re-emit-nullable`
 
 For every `contract.json` matched by `detection`, run the extension package's `build:contract-space` script (or its emit command) once after upgrading. The expected diff is one `"nullable"` boolean per to-one relation in `contract.json`, plus the `Models` namespace, `models` constant, and `RelationKeys` import in `contract.d.ts`.
+
+## `schema-header-use-prisma-8`
+
+For every `.prisma` file matched by `detection`, replace the first-line header `// use prisma-next` with `// use prisma-8`. Nothing else in the file changes.
+
+## `env-vars-drop-next-infix`
+
+For every file matched by `detection`, replace the `PRISMA_NEXT_` prefix with `PRISMA_` on each environment variable name.