Repository navigation
Conversation
…nd release status (prisma#8245) * docs(docs): add a Prisma ORM release status page New page at /prisma-orm/release-status, the answer to "should I move to Prisma ORM 8 now" (audit C4, job J4). Added to the Getting Started > Prisma ORM sidebar after the index page. Two placeholders are left for Will: the GA window and the Prisma ORM 7 support period. Sources for every claim on the page: - Release candidate, runtime version 8.0.0-rc.9: wip/prisma-src/packages/9-public/@prisma/orm-postgres/package.json:3 ("version": "8.0.0-rc.9"), confirmed by `pnpm view @prisma/orm-postgres dist-tags` -> { latest: '8.0.0-rc.9' }. - CLI version 8.0.0-rc.13 on its own release line: `pnpm view prisma dist-tags` -> { next: '8.0.0-rc.10', prev: '7.10.0', latest: '8.0.0-rc.13' }; `pnpm view prisma version` -> 8.0.0-rc.13. The CLI's latest runs ahead of the runtime's, which is why the page states both. - `@prisma/client@latest` is still 7.x: `pnpm view @prisma/client dist-tags` -> { latest: '7.10.0', prev: '6.19.3' }. Checked 11 September 2026; the page says so. - The Prisma ORM 8 CLI has no `generate`, `migrate dev` or `db push` command: wip/prisma-src/packages/1-framework/3-tooling/cli/src/orm/cli.ts:98-121 (the whole mounted command tree). - Prisma ORM 7 doc locations: apps/docs/content/docs/orm/v7/index.mdx:4 (url: /orm/v7), apps/docs/content/docs/(index)/v7/getting-started.mdx:4 (url: /v7/getting-started), apps/docs/content/docs/cli/v7/index.mdx:6 (url: /cli/v7). - The side-by-side migration guide: apps/docs/content/docs/guides/upgrade-prisma-orm/postgresql.mdx:4 (url: /guides/upgrade-prisma-orm/postgresql). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): add a Coming from Prisma ORM 7 mapping page New page at /orm/coming-from-prisma-orm-7 (audit C1, job J3): four tables mapping Prisma ORM 7 schema attributes, CLI commands, and client methods onto their Prisma ORM 8 forms, plus a "not in Prisma ORM 8 yet" table with a status per row. Added to the ORM sidebar's Introduction group after Core concepts. The incremental upgrade guide is linked in the second paragraph. One row is marked for Will to confirm: the status of the generated model and payload types. Everything was verified against the prisma/orm monorepo at rc.9 under wip/prisma-src. Paths below are relative to it unless noted. Schema and types - Native types in type position, and the full Postgres type list: packages/2-sql/2-authoring/contract-psl/README.md:21; the removed `@db.*` attributes produce "@db.X(args) is no longer supported; use X(args) in type position", built at packages/2-sql/2-authoring/contract-psl/src/psl-attribute-parsing.ts:31. Before/after in docs/releases/v0.17.0.md:53-68. - `@db.Text` -> `String`: `String` binds native `text`, packages/3-extensions/postgres/test/scalar-type-parity.test.ts:67 ("String: { codecId: 'pg/text@1', nativeType: 'text' }") and packages/3-targets/3-targets/postgres/src/core/psl-infer/postgres-type-map.ts:4 ("text: 'String'"). There is no `Text` constructor, which is why the page warns that the generic hint is misleading here. - `@db.VarChar(n)` -> `VarChar(n)`: packages/3-targets/6-adapters/postgres/src/core/control-mutation-defaults.ts:206-214. - `@db.Decimal(p,s)` -> `Numeric(p, s)`: `Decimal` is a zero-arg constructor for unconstrained numeric (control-mutation-defaults.ts:183-186) while `Numeric` takes precision and scale (:224-238); introspection maps both `numeric` and `decimal` to `Numeric` (postgres-type-map.ts:28-29). - `@db.Uuid` -> `Uuid`: control-mutation-defaults.ts:275; live use at examples/prisma-8-demo/src/prisma/contract.prisma:28. - `DateTime` stays, as Temporal-backed timestamptz: packages/3-extensions/postgres/test/scalar-type-parity.test.ts:76. - `@updatedAt` -> `temporal.updatedAt()`: rejection and hint at packages/2-sql/2-authoring/contract-psl/src/psl-field-resolution.ts:196-198, prose at contract-psl/README.md:67-72. - `cuid()` -> `cuid(2)`: contract-psl/README.md:62-64; the signature requires the version argument, packages/3-targets/6-adapters/postgres/src/core/control-mutation-defaults.ts:122,141. - `Json` vs `Jsonb`: both exist (scalar-type-parity.test.ts:77-78), and docs/releases/v0.17.0.md:49 states that a pre-0.16 `Json` field means `Jsonb` now. - `// use prisma-next` on the first non-whitespace line: docs/releases/v8.0.0-rc.9.md:57; matcher at packages/1-framework/3-tooling/language-server/src/schema-directive.ts:1. - `generator` and `datasource` gone: the parser reserves only `model`, `namespace`, `type`, `types` (packages/1-framework/2-authoring/psl-parser/src/parse.ts:499-504) and any other top-level block is rejected with PSL_UNSUPPORTED_TOP_LEVEL_BLOCK (contract-psl/src/interpreter.ts:2121,2134-2135). The config envelope shown on the page is examples/prisma-8-demo/prisma.config.ts:1-18; the four keys of the inner `ormConfig` are packages/3-extensions/postgres/src/config/define-config.ts:16-25. - Surviving attributes: the closed registry at packages/2-sql/2-authoring/contract-psl/src/sql-attribute-specs.ts:467-486. - Enums: `@@type` is the only block attribute an `enum` declares (packages/2-sql/9-family/src/core/authoring-entity-types.ts:149-157); members may be bare or valued, examples/prisma-8-demo/src/prisma/contract.prisma:14-25. `native_enum` is the real Postgres enum type and does take `@@map`: packages/3-targets/3-targets/postgres/src/core/authoring.ts:302,324 and test/integration/test/authoring/parity/native-enum/schema.prisma:16-25. - Scalar lists rejected, implicit many-to-many rejected: contract-psl/README.md:50-58; the junction model's `@@id([...])` requirement at contract-psl/src/psl-relation-resolution.ts:304,312. CLI commands - The whole mounted command tree, which is what every "no equivalent" in the table rests on: packages/1-framework/3-tooling/cli/src/orm/cli.ts:98-121. It has no `generate`, `migrate dev`, `migrate deploy`, `db push`, `db pull`, `migrate diff`, `migrate resolve`, `db seed`, `studio` or `validate`. - `prisma contract format` replaces `prisma format`, and skips a TypeScript contract: packages/1-framework/3-tooling/cli/src/orm/format.ts:33-41. - No seed hook in the config either: packages/3-extensions/postgres/src/config/define-config.ts:16-25. - `prisma studio --url` is the Prisma ORM 8 path for Studio; that is a platform CLI command, not an ORM one, so the source is this repo: apps/docs/content/docs/studio/getting-started.mdx:37. Client API - Client construction, `db.transaction`, `db.raw`, `db.connect()`, `db.close()`: the PostgresClient interface, packages/3-extensions/postgres/src/runtime/postgres.ts:56-74; `connect()` is at-most-once (:299-301). Documented `db.ts` shape on this site: apps/docs/content/docs/guides/making-guides.mdx:137-146. - Every collection method in the table: packages/3-extensions/sql-orm-client/src/collection.ts — where:326, include:495, select:666, orderBy:717, groupBy:765, distinct:910, distinctOn:945, limit:978, offset:993, all:1038, first:1066, aggregate:1126, create:1235, createAll:1339, createAndCount:1656, upsert:1732 (`conflictOn` at :1694-1699), update:1867, updateAll:1956, updateAndCount:2031, delete:2081, deleteAll:2122, deleteAndCount:2235. There is no `count()` terminal; counting goes through `aggregate((agg) => ({ ... agg.count() }))`, :1106-1120. - Namespace-qualified accessor: packages/3-extensions/sql-orm-client/src/orm.ts:88,156-201. - Raw SQL terminators: packages/2-sql/4-lanes/sql-builder/src/types/raw-query.ts:139-142,154-166; the `$queryRaw`/`$executeRaw` mapping is stated in docs/releases/v8.0.0-rc.2.md:120. Not in Prisma ORM 8 yet - `skipDuplicates`: absent (scorecard/06-sql-orm-client.md:62); `createAll` takes no options object (collection.ts:1339-1346); the `upsert` with `update: {}` workaround is documented at collection.ts:1717-1729. - Atomic increment/decrement: absent (scorecard/12-nested-writes-and-atomic-ops.md:34-37); the update input is a plain partial row, packages/3-extensions/sql-orm-client/src/types.ts:1779-1784. - `findUniqueOrThrow`/`findFirstOrThrow`: absent (scorecard/06-sql-orm-client.md:60); the workaround `.all().firstOrThrow()` throws RUNTIME.NO_ROWS, packages/1-framework/1-core/framework-components/src/execution/async-iterable-result.ts:68-77. - `mode: "insensitive"`: absent (scorecard/09-filtering.md:33); `.ilike` exists on textual columns, packages/3-targets/6-adapters/postgres/src/core/descriptor-meta.ts:155-167. The core operator set (no contains/startsWith/endsWith) is packages/3-extensions/sql-orm-client/src/types.ts:360-413. - JSON filters: absent (scorecard/09-filtering.md:34); the `json` codec declares no traits and `jsonb` only `equality`, packages/3-targets/3-targets/postgres/src/core/codecs.ts:1400-1402,1444. - `$transaction([...])`: only the callback form exists, packages/3-extensions/postgres/src/runtime/postgres.ts:67,341-372. - Model and payload types: `Models` was removed in 0.14 (docs/releases/v0.14.0.md:28) and no `Shape<>` exists in this checkout; `DefaultModelRow` is the closest, packages/3-extensions/sql-orm-client/src/types.ts:510-521. No product statement covers what ships next, so the row is marked for Will. - `$use` -> runtime middleware: packages/1-framework/1-core/framework-components/src/execution/runtime-middleware.ts:168-182; wired as constructor config, packages/3-extensions/postgres/src/runtime/postgres.ts:78. - `$extends`: absent in all four component kinds, scorecard/18-extensions.md:26-29. - The bulleted extras: nested writes (scorecard/12-nested-writes-and-atomic-ops.md:27-33), scalar-list filters (scorecard/09-filtering.md:35-38), transaction options (scorecard/14-transactions.md:18-23), omit / relationLoadStrategy / Prisma.skip / findUnique batching (scorecard/06-sql-orm-client.md:61,63-67), the P-code taxonomy (scorecard/19-observability-and-lifecycle.md:18,21-27), the `Prisma.sql` family and TypedSQL (scorecard/13-raw-and-typed-sql.md:18-23), and soft delete, validations, callbacks and read replicas (skills/prisma-8/references/contract.md:392-395, skills/prisma-8/references/runtime.md:323). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): link the two new upgrader pages from the ORM entry points The two pages added in this branch are only useful if the Upgrader lands on them, and today every Prisma ORM 7 pointer on the site is for staying on 7 (audit A2). Added to the shared "Using Prisma 7?" note box, both links: - orm/index.mdx - cli/index.mdx - (index)/prisma-orm/index.mdx - (index)/prisma-orm/quickstart/postgresql.mdx - (index)/prisma-orm/add-to-existing-project/postgresql.mdx Release status only, since the mapping page is PostgreSQL: - (index)/prisma-orm/quickstart/mongodb.mdx - (index)/prisma-orm/add-to-existing-project/mongodb.mdx - guides/postgres/vercel.mdx, whose Prisma 7 note is about the postinstall hook Elsewhere: - (index)/index.mdx: the ORM line now also points at release status - (index)/getting-started.mdx: one sentence under the opening line - orm/fundamentals/reading-data.mdx: the existing "For Prisma 7 users" block, which is where the accessor change is stated, now points at the page that maps the rest of the API Not touched: the sixteen Prisma 7 guides under audit A7, which are being moved in another branch, and guides/making-guides.mdx. Verified with `apps/docs/node_modules/.bin/tsx ./scripts/lint-links.ts` from apps/docs: 705 files, 0 errors. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): review fixes on the two upgrader pages - scalar lists are supported on PostgreSQL (adapter.ts:38 declares sql.scalarList; capability-gating test rejects only sqlite); only the list filters are absent. - @@type on an enum is optional since 0.15 (framework-authoring.ts:330-347, interpreter.enum.test.ts:624-700); a Prisma ORM 7 enum carries over. - the Prisma ORM 8 CLI has no studio command (cli.ts:95-121); Studio runs from the Prisma ORM 7 CLI with --url, as studio/prisma-next.mdx says. - the orm config section has five keys including output (define-config.ts:16-26); the sample uses definePrismaConfig from prisma/config like every other Prisma ORM 8 page. - Json columns still take isNull/isNotNull (types.ts:404-410). - DateTime is Temporal-backed; Node.js 26.8.2 ships Temporal, earlier releases need temporal-polyfill/full/global. - model and result types: Models, models, Scalars, Shape, ResultType are in prisma/orm main (#30231) and ship with the next tagged release. - link labels follow the naming rule. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): spellcheck SQLSTATE; do not promise a support period the status page cannot give yet Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): correct three claims on the Coming from Prisma ORM 7 page - Temporal: Node.js 26.0.0 already ships the global Temporal object (verified with `npx node@26.0.0 -p "typeof Temporal"` -> object), so the row now says "Node.js 26 and later", matching the existing add-to-existing-project page, instead of "26.8.2 and later". - `prisma db push` -> `prisma db update`: nothing on the site says `db update` signs the database; the CLI page documents that it advances the `db` ref when run without `--db`. The row now says that. - Error codes: the error reference documents `sqlState` only on connection and migration-apply envelopes, not on query-time constraint errors, so the `23505` claim is dropped; the bullet now points at `RUNTIME.NO_ROWS`, which is documented. With that sentence gone, the `SQLSTATE` cspell word added in the previous commit has no remaining use, so it is removed again. * docs(docs): Temporal availability by Node.js line; link the db update reference Checked: official Node.js 26.0.0 and 26.8.1 expose globalThis.Temporal; Homebrew's 26.8.1 build does not; 25.8.0 does not. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): state the GA window and the Prisma ORM 7 support period Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): write the two upgrader pages for a reader who has not seen the internals Same facts; the wording no longer assumes the reader knows what a release line, a codec, a terminal call, an envelope, or a junction model is. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): drop two source-code terms the plain-language check caught Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): answer what the reader review could not: db.ts, install, raw SQL, many-to-many Show src/prisma/db.ts and the install command; split the DateTime note out of the table; explain // use prisma-next and the temporal./pg. helpers; make the raw SQL row a runnable example; show the many-to-many contract; say what replaces $use and $extends for the reader's use; one meaning for 'available in a different form'. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): second reader-review round on the upgrader pages Side-by-side needs the @prisma/prisma7 package; what first() returns on no match; the aggregate result shape; nested create; how to catch a unique-constraint violation; what db.orm and db.runtime() are; db init versus db update; requirements on the status page; less mechanism. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): third reader-review round on the upgrader pages A 'Before you start' block with the install commands and orm init; the db push row no longer contradicts db init; the enum row says storage changed and when to use native_enum; migrate resolve split into its two cases with the ref defined in the sentence; the raw SQL rule stated as a rule; contains in the queries table; the many-to-many example declared complete; one-line fixes on the status page (lock command, lock file, dist-tags, the @prisma/prisma7 install). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): fourth reader-review round on the upgrader pages What to do with an existing schema.prisma; the everyday loop after migrate dev; a warning not to install prisma@8 alone in a version 7 app; query results are typed as written; a complete upsert; reuse contract column types in raw queries; the blocker list on the status page. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): say release candidate where the pages point at release status Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): make the Prisma ORM 7 support heading state the answer Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): state the Prisma ORM 6 support period Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): Prisma ORM 6 gets security patches, not support Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): the status page points at the migration guide instead of repeating it Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): coming-from page: complete commands, one command form, sections that name their subject - 'Before you start' gives the install and setup commands in full and says what orm init writes (it does install dotenv: cli/src/orm/init.ts:138). - commands are written as 'prisma ...' in tables and run as 'npx prisma ...'. - the side-by-side install points at step 1 of the migration guide, not the status page. - headings: 'schema.prisma is now contract.prisma'; 'src/prisma/db.ts replaces PrismaClient' is its own section ahead of 'Queries'. - the DateTime note is short sentences: DateTime returns Temporal.Instant by definition, other types return other things; Node.js 26 has Temporal, 22 and 24 do not, add the polyfill line; Homebrew's 26 lacks it. - the config keys are a list. - $extends will not be added; use middleware. skipDuplicates row says createMany itself is createAll/createAndCount. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): keep the #schema anchor on the renamed heading Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): fix four facts in the not-available section DefaultModelRow is not exported from contract.d.ts; the next release emits Models, Shape and ResultType instead. Nested disconnect works. sqlState is the normalized SQL state, not a Postgres-only code. The $extends row links to the middleware page instead of pointing at another row. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): one sentence for the $extends row Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): four reader-review rounds on the coming-from page Each round handed the page to a fresh reader with the Prisma ORM 7 persona and every mark was fixed: .env step, install warning before the install block, unchanged scalar types row, namespace row, join-table rule, upsert conflictOn explained, migrate reset and diff rows, dotenv in the config sample, model types today, list filters via raw SQL. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): two more reader rounds and a fact re-check on the coming-from page Reader rounds five and six: install paragraph, join-table rule stated as a requirement, A/B column rule, upsert conflictOn, middleware example, raw SQL takes types from the table, general rule for @db. types, DateTime is timestamptz, old prisma/ folder stays until the guide removes it. Fact re-check against rc.9: native_enum members need explicit values, table names are the model name with a lowercase first letter, init also writes prisma-next.md and sets tsconfig types, migrations dir is relative to the config file, a PostTag[] field is unnecessary rather than forbidden. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): Before you start is two cases, not a half tutorial Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): @@Map on enum is rejected by contract emit, verified with rc.13 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> Co-authored-by: reviewer <reviewer@users.noreply.github.com>
…der before a page ships (prisma#8247) * docs: add the docs-reader-review skill A page written from the source reads like the source: vocabulary from the code, mechanism instead of action, several ideas per sentence. A fact review does not catch it because every such sentence is true. This skill is the missing step: a banned-term check, then a fresh reviewer with only the reader's knowledge reads the page cold and marks what it cannot follow, then fix, repeat, and re-check the facts, because reader rounds drift meaning. Validated per the skill-authoring guide: the same writing task run without the skill produced 'a diff between two contracts', 'resolve an origin contract', 'an explicit --db binding'; with the skill it ran six reader rounds and produced plain text, and drifted two facts, which is the loophole the 'Facts stay fixed' rule and step 5 now close. docs-writer's final checklist requires this pass; the skills README lists it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs: narrow the banned-term check so 'terminal output' is not a hit Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs: make the banned-term check cover the list, every code-block form, and a testable definition exception - the pattern covers every unconditional row of banned-terms.md (capability, the lane and junction forms, buffers/materializes, and the verb phrases); the rows marked (unexplained) are stated to be the reviewer's, since a regex cannot tell a defined term from a bare one. - fenced code with backticks or tildes, indented or not, indented code blocks, and inline code are stripped before matching. - a line carrying {/* plain-language:defined */} is skipped; the skill and the list say when that marker is allowed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
… user can read them (prisma#8251) * docs(orm8): reader-review round one on the five fundamentals pages Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): reader-review rounds two to four on the fundamentals pages Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): fact re-check corrections on transactions and reading-data Commit-time write conflicts arrive as RUNTIME.TRANSACTION_COMMIT_FAILED with the database error on cause; the retry helper unwraps it. Timestamp filters take Temporal.Instant, not Date. idle_in_transaction_session_timeout, not statement_timeout, bounds a transaction. Only for-await consumes a result; awaiting twice is fine. Aggregate and operator lists completed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): relations page samples match the models they show Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): fact re-check corrections on writing-data MongoDB contracts have no @default; execute() resolves to { affectedRows }; inc and mul are for number fields; awaiting twice is fine, mixing forms throws; the error reference lists Prisma ORM's own codes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): fact re-check corrections on advanced-queries Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): sample ids the spell checker accepts Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): MongoDB id note under the advanced-queries contract; select narrows the type on PostgreSQL only Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(orm8): race-free connectOrCreate replacement; bind tx in the isolation example Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* docs(docs): update the Prisma ORM 8 pages for 8.0.0-rc.10 Schema header is // use prisma-8, orm init writes prisma-8.md, db sign sets the db ref so adopting an existing database is one command, contract.d.ts exports Models with Scalars, Shape, and ResultType, and the release status and upgrade guides target rc.10. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(docs): review fixes on the rc.10 pages Check both packages dist-tags on the release status page; say that db sign --no-advance-ref skips the snapshot as well as the ref, which is what cli/src/orm/db/sign.ts does. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
cursor
Bot
force-pushed
the
cursor/fix-compute-cli-docs-8148-cd0c
branch
from
September 12, 2026 13:38
e7c3f58 to
2af8cb7
Compare
…resets Align Code Hike fallback animations with the unified Prisma CLI (npx prisma@latest): project create, git connect, and git push instead of the removed app deploy and database command groups. Fixes prisma#8148
cursor
Bot
force-pushed
the
cursor/fix-compute-cli-docs-8148-cd0c
branch
from
September 12, 2026 13:38
2af8cb7 to
5a0c805
Compare
Owner
Author
|
Closing: branch drifted with unrelated docs/.claude changes. Will open a minimal presets-only PR for any remaining @prisma/cli@latest strings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the remaining gap from prisma#8148 after the Compute MDX pages were migrated to the unified
prisma@latestCLI in prisma#8151 and follow-ups.The eleven pages under
apps/docs/content/docs/compute/already document the current command set (project,git,service,postgres, Composerdeploy, and so on) and no longer reference@prisma/cli@latestor the removedapp/databasecommand groups.This change updates the Code Hike fallback concept-animation presets (
compute-model,github-connection,env-layers) so they match the same workflow shown in the pages and in the primary flow animations:npx prisma@latest project create,git connect, andgit pushinstead ofnpx @prisma/cli@latest app deploy.Test plan
rg '@prisma/cli@' apps/docsreturns no matchesFixes prisma#8148