chore(deps): move the ORM family to 8.0.0-rc.10

[wmadden-electric]

Moves every @prisma/orm-* pin from 8.0.0-rc.8 to 8.0.0-rc.10 (rc.9 was skipped). Precedes the v0.19.0 release PR.

• Schema files use the new // use prisma-8 header (the old one still works but is deprecated in rc.10).
• Every committed contract was re-emitted with the rc.10 toolchain: contract.json gains the nullable flag on to-one relations, contract.d.ts gains the Models namespace. The migrations/snapshots/<hash>/contract.d.ts copies are synced, as the contract-snapshot lint requires. Storage hashes are unchanged, so no migration or snapshot content changed.
• Verified locally: build, typecheck, lint, lint:deps, check:publish-deps, test:scripts, and every test package run one at a time (the suite shares one local Postgres, so parallel runs interfere on a laptop).

🤖 Generated with Claude Code

[prisma-gizmo]

✅ Gizmo reviewed 10280c9 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This PR moves every @prisma/orm-* pin from 8.0.0-rc.8 to 8.0.0-rc.10 (skipping the never-released rc.9) and re-emits every committed contract with the rc.10 toolchain, preparing the repo for the v0.19.0 release.

Dependency pins. All seven touched package.json files move in lockstep: @prisma/orm-postgres and @prisma/orm-toolchain keep their exact-pin policy (no ranges) in dependencies, devDependencies, and the peer dependency on composer-prisma-cloud. No rc.8 references remain outside the lockfile, which was regenerated in the same commit.

Schema headers. Every contract.prisma — the four example packages, the auth pack, and the fixture sources — swaps the deprecated // use prisma-next header for // use prisma-8; a repo-wide search confirms none of the old headers survive.

Re-emitted contracts. The rc.10 emitter's output changes show up three ways, applied consistently across all committed contracts:

• contract.d.ts gains the new Models namespace and declare const models export plus the RelationKeys import (empty in examples/auth, populated per model elsewhere).
• contract.json gains "nullable": false on to-one/N:1 relations, matching the readonly nullable: false additions in the auth pack's relation type declarations.
• Generated-file stamps rename from prisma-next contract emit to prisma contract emit.

The gadget/widget test fixtures show the fullest re-emission diff: aggregate types split (avg/avgDecimal, sum/sumBigInt), the pg/time@1/pg/timestamp@1 codecs renamed to their -string/-temporal variants, unboundedint/int8number codecs added, and the sql.checkConstraint capability flag. The three example migrations/snapshots/<hash>/contract.d.ts copies are byte-identical to their parent contract.d.ts (verified by diff), as the contract-snapshot lint requires; storage hashes are untouched, so no migration content changed.

Incidental catch-up. Re-emitting examples/auth also bumps its auth extension reference from 0.14.0 to 0.18.0, aligning it with the workspace auth pack version released in v0.18.0 rather than being a version change this PR introduces.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 18f98194-ae10-4e90-b516-e1a58ab60937

---

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@prisma/composer@291

npm i https://pkg.pr.new/@prisma/composer-cli@291

npm i https://pkg.pr.new/@prisma/composer-prisma-cloud@291

commit: 10280c9

[prisma-gizmo]

New findings: 🟡 1 minor · trace

Findings outside the diff

• 🟡 Minor · consistency packages/1-prisma-cloud/2-shared-modules/auth/src/tests/fixtures/empty-app/emitted/contract.d.ts — empty-app fixture's emitted contract.d.ts was not re-emitted and still bears the old 'prisma-next contract emit' header
  The PR description states every committed contract was re-emitted with the rc.10 toolchain, and indeed the gadget/widget fixture emitted/contract.d.ts and emitted/contract.json files were regenerated (generator stamp renamed from prisma-next contract emit to prisma contract emit). However, packages/1-prisma-cloud/2-shared-modules/auth/src/__tests__/fixtures/empty-app/emitted/contract.d.ts (lines 2-3) — a tracked file, referenced by pack-conformance.integration.test.ts — still carries the old prisma-next contract emit generator header, even though this PR migrated the fixture's own source/contract.prisma to the new // use prisma-8 header. The emitted fixture is now stamped by a toolchain version the PR is moving away from, inconsistent with the other fixtures and with the PR's re-emit claim.
  Recommended fix: Re-run prisma contract emit for the empty-app fixture (or apply the same rc.10 header/message rename used in the gadget/widget fixtures) so all committed emitted contracts carry the rc.10 generator stamp.

[prisma-gizmo]

All Gizmo review threads are resolved and the head commit has been reviewed. Approving.