chore(deps): move the ORM family to 8.0.0-rc.13 - #322
Conversation
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>
|
✅ Gizmo reviewed 6350d86 — posted 1 inline comment(s) this pass. Open findings: 🟡 1 minor Change walkthroughThis PR moves the whole ORM dependency family ( Dependency pins — The version bump spans seven Contract re-emits — Contracts for Hand-migrated snapshot — The orders migration snapshot under Nothing else in the repo consumes the changed contract fields or the old ref shape, so no callers were left behind. |
|
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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Essentials Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (19)
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
WalkthroughPackage 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 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)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
commit: |
|
@prisma-gizmo review |
Linked issue
n/a — dependency move. Context:
prisma@8.0.0-rc.18ships@prisma/orm-toolchainrc.13, while Composer 0.24.0 still requires@prisma/orm-postgresrc.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-postgresand@prisma/orm-toolchainto8.0.0-rc.13(the peer in@prisma/composer-prisma-cloudincluded), 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 emitwith the rc.13 toolchain). Execution default refs now readentry/field, andexecutionHashmoves. The one migration snapshot with an execution section (examples/store/modules/orders) is renamed by hand, as the guide prescribes.storageHashorprofileHashmoves, so no migrations. The auth pack's contract is unchanged (head9e4dbce…).examples/auth: its contract's stale auth pack label (0.22.0) is refreshed by the re-emit..ref.table/.columnreads, noapplyMutationDefaults, 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 lintpnpm turbo run test: 66/66 taskspnpm check:publish-deps,check:family-static-graph,check:npm-effect-resolution,check:skill-packagingChecklist
git commit -s) per the DCO.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:pinsstrict.🤖 Generated with Claude Code