Skip to content

chore(deps): move the ORM family to 8.0.0-rc.13 - #322

Merged
kristof-siket merged 1 commit into
mainfrom
chore/orm-rc.13
Sep 29, 2026
Merged

kristof-siket merged 1 commit into
mainfrom
chore/orm-rc.13

Conversation

@kristof-siket

Copy link
Copy Markdown
Contributor

Linked issue

n/a — dependency move. Context: prisma@8.0.0-rc.18 ships @prisma/orm-toolchain rc.13, while Composer 0.24.0 still requires @prisma/orm-postgres rc.12 exactly. No set of pins in a project (e.g. create-prisma, prisma/create-prisma#118) can match both, so this brings Composer to rc.13.

Summary

Moves @prisma/orm-postgres and @prisma/orm-toolchain to 8.0.0-rc.13 (the peer in @prisma/composer-prisma-cloud included), following the ORM's rc.12 → rc.13 upgrade guide (skills/prisma-8/upgrading/{app,extension}/upgrades/8.0.0-rc.12-to-8.0.0-rc.13):

  • execution-ref-entry-field: every contract re-emitted (prisma contract emit with the rc.13 toolchain). Execution default refs now read entry/field, and executionHash moves. The one migration snapshot with an execution section (examples/store/modules/orders) is renamed by hand, as the guide prescribes.
  • Hashes: no storageHash or profileHash moves, so no migrations. The auth pack's contract is unchanged (head 9e4dbce…).
  • examples/auth: its contract's stale auth pack label (0.22.0) is refreshed by the re-emit.
  • Nothing else applies: detection for the remaining Postgres entries found nothing (no .ref.table/.column reads, no applyMutationDefaults, no moved temporal/generator imports, no literal TS .default(, no unformatted contract sources). The Mongo entries don't apply.

Testing performed

  • pnpm build && pnpm typecheck && pnpm lint
  • pnpm turbo run test: 66/66 tasks
  • pnpm check:publish-deps, check:family-static-graph, check:npm-effect-resolution, check:skill-packaging

Checklist

  • All commits are signed off (git commit -s) per the DCO.
  • I read CONTRIBUTING.md and the change is scoped to one logical concern.
  • The PR title is a conventional commit.
  • Tests are updated (re-emitted fixtures).

Notes for the reviewer

Next: release Composer 0.25.0, then prisma-cli follows (its toolchain is already rc.13), then create-prisma can pin all three together and keep check:pins strict.

🤖 Generated with Claude Code

Pins @prisma/orm-postgres and @prisma/orm-toolchain at 8.0.0-rc.13, matching
the toolchain prisma 8.0.0-rc.18 ships. Following the rc.12 to rc.13 upgrade
guide: every contract is re-emitted (execution default refs now name
entry/field), and the orders migration snapshot's refs are renamed by hand.
No storage or profile hash changes, including the auth pack head.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Kristof Siket <siket@prisma.io>
@prisma-gizmo

prisma-gizmo Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

✅ Gizmo reviewed 6350d86 — posted 1 inline comment(s) this pass.

Open findings: 🟡 1 minor

Change walkthrough

This PR moves the whole ORM dependency family (@prisma/orm-postgres, @prisma/orm-toolchain, plus the peer in composer-prisma-cloud) from 8.0.0-rc.12 to 8.0.0-rc.13, and re-emits the affected contract fixtures to match the rc.13 toolchain's new default-ref shape.

Dependency pins — The version bump spans seven package.json files (examples, the target extension, the shared auth module, and the public composer-prisma-cloud package). Every pin moved in lockstep, exact-versioned as before, and no straggler rc.12 pins for the ORM family remain anywhere in the repo (the remaining rc.12 hits are the unrelated @distilled.cloud/prisma package). The checked-in pnpm-lock.yaml already resolves only rc.13 for both ORM packages, so the pins and lockfile agree at head.

Contract re-emits — Contracts for examples/orm-demo, examples/store/modules/orders, and the target extension's gadget/widget test fixtures were regenerated: mutation-default refs changed from { column, table } to { entry, field } and executionHash values moved accordingly, with no storageHash/profileHash changes (hence no new migrations). Each .d.ts agrees with its JSON twin and with other files hashing identical execution content — orm-demo and the widget fixture agree on 135e2930…, and the gadget fixture is self-consistent. The examples/auth contract refresh also picks up the auth extension label 0.22.0 → 0.24.0, which now matches the auth shared module's actual version; no stale 0.22.0 labels remain in any contract.

Hand-migrated snapshot — The orders migration snapshot under examples/store/modules/orders/migrations/snapshots/a2c3b473… was hand-edited per the upgrade guide (its directory name is the unchanged storageHash) to apply the ref reshape.

Nothing else in the repo consumes the changed contract fields or the old ref shape, so no callers were left behind.

@coderabbitai

coderabbitai Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Essentials

Run ID: 3276033a-2d24-4fd4-bd6d-1c65b9d9c26f

📥 Commits

Reviewing files that changed from the base of the PR and between ee6846d and 6350d86.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (19)
  • examples/auth/contract.d.ts
  • examples/auth/contract.json
  • examples/auth/package.json
  • examples/orm-demo/contract.d.ts
  • examples/orm-demo/contract.json
  • examples/orm-demo/package.json
  • examples/store/modules/catalog/package.json
  • examples/store/modules/orders/contract.d.ts
  • examples/store/modules/orders/contract.json
  • examples/store/modules/orders/migrations/snapshots/a2c3b4739043e9c6f4f73292efb624bb2f1a9be70503e580c9dc7b34b6d366cf/contract.d.ts
  • examples/store/modules/orders/migrations/snapshots/a2c3b4739043e9c6f4f73292efb624bb2f1a9be70503e580c9dc7b34b6d366cf/contract.json
  • examples/store/modules/orders/package.json
  • packages/1-prisma-cloud/1-extensions/target/package.json
  • packages/1-prisma-cloud/1-extensions/target/src/__tests__/fixtures/gadget-contract/emitted/contract.d.ts
  • packages/1-prisma-cloud/1-extensions/target/src/__tests__/fixtures/gadget-contract/emitted/contract.json
  • packages/1-prisma-cloud/1-extensions/target/src/__tests__/fixtures/widget-contract/emitted/contract.d.ts
  • packages/1-prisma-cloud/1-extensions/target/src/__tests__/fixtures/widget-contract/emitted/contract.json
  • packages/1-prisma-cloud/2-shared-modules/auth/package.json
  • packages/9-public/composer-prisma-cloud/package.json

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.


Summary by CodeRabbit

  • Updates
    • Updated example projects and shared packages to the latest ORM tooling release.
    • Refreshed generated example contracts to reference ID defaults by model field, keeping contract output aligned with the updated format.

Walkthrough

Package versions for Prisma ORM dependencies changed from 8.0.0-rc.12 to 8.0.0-rc.13. The auth extension version changed from 0.22.0 to 0.24.0. Example contracts, a migration snapshot, and emitted fixtures now reference defaults by entry and field instead of table and column. Associated execution hashes changed.

Priority: ➖ Normal

Merge Risk: ⚪ Minimal · up to 6350d

No additional actionable merge-blocking issue is established for this change. The previously reported snapshot-hash concern remains available for the owner to assess.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the primary change: moving the ORM dependencies to version 8.0.0-rc.13.
Description check ✅ Passed The description directly explains the dependency upgrades, contract re-emission changes, migration snapshot updates, and validation performed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 6…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
✨ Simplify code
  • Commit to this branch
  • Create a new PR

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

@pkg-pr-new

pkg-pr-new Bot commented Sep 29, 2026

Copy link
Copy Markdown

Open in StackBlitz

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

commit: 6350d86

@prisma-gizmo prisma-gizmo Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New findings: 🟡 1 minor · trace

@kristof-siket

Copy link
Copy Markdown
Contributor Author

@prisma-gizmo review

@prisma-gizmo prisma-gizmo Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@kristof-siket
kristof-siket merged commit 2a7b056 into main Sep 29, 2026
30 of 31 checks passed
@kristof-siket
kristof-siket deleted the chore/orm-rc.13 branch September 29, 2026 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant