Repository navigation
chore(deps): move Composer to Prisma ORM 8.0.0-rc.17 and CLI engine 0.7.0 - #345
Conversation
The Prisma CLI ships @prisma/cli-engine 0.7.0 since prisma/prisma-cli#337. Engine 0.7.0 is a minor release that adds API and error codes and removes nothing, so only the pins move. Signed-off-by: Kristof Siket <siket@prisma.io>
|
✅ Gizmo reviewed 25a43de — posted 0 inline comment(s) this pass. Open findings: none Change walkthroughThis PR is a coordinated dependency bump: Composer moves to Prisma ORM Version pins. The Auth contract re-emit. The rc.17 upgrade guide Auth migration re-authoring. The pack's No stale references to the old hash, |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (20)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. 3 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. Summary by CodeRabbit
WalkthroughThe PR updates Prisma ORM, toolchain, and CLI engine versions across examples and packages. It refreshes the generated PostgreSQL auth contract with model types, field and relation mappings, capabilities, indexes, and storage hashes. Auth migration SQL changes timestamp types to unquoted Estimated code review effort Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to The upgrade can proceed with the documented database re-sign step for existing auth deployments. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
commit: |
Pins @prisma/orm-postgres and @prisma/orm-toolchain at 8.0.0-rc.17 in all seven manifests. ORM rc.17 peers @prisma/cli-engine 0.7.0, the engine this branch already pins. Following the rc.16 to rc.17 guides, the entries whose detection matches Composer: - foreign-keys-name-their-backing-index and its extension twin: one re-emit of every contract with the rc.17 toolchain. Only the auth pack has foreign keys whose backing index the contract now names (account_userId_idx, session_userId_idx), so only its storage hash changes. - orm-collections-lock-rows and contract-artifacts-restamp: covered by the same re-emit; no other emitted file changes. - enum-codecs-refused and with-is-a-collection-member: false matches. The first is a timestamptz-string codec on a plain column, the second an import attribute. The auth pack's 0001_init is re-authored with migration plan, as the pack's prisma.config.ts describes. Its operations are the same; the rc.17 renderer writes timestamptz unquoted. examples/auth re-materialises the auth space from the pack: 0001_init, refs/head.json, and the snapshot directory move to the new hash. Storage hashes (old -> new): - auth pack head, and the auth space in examples/auth: 310f206d -> 0df0ef09 An auth database deployed with an earlier Composer has its marker at 310f206d. Run prisma db sign against it before its next deploy. Signed-off-by: Kristof Siket <siket@prisma.io>
kristof-siket
changed the title
![prisma-gizmo[bot]](https://avatars.githubusercontent.com/in/4769794?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Re-runs pnpm bump-minor on top of main to resolve the version conflicts with #345. Signed-off-by: Kristof Siket <siket@prisma.io>
…rc.15; release v0.29.1 (#349) * fix(deps): go back to alchemy 2.0.0-beta.78 so npm stops nesting prisma@8.0.0-rc.15 alchemy 2.0.0-beta.80 and later declare optional peers on exactly prisma@8.0.0-rc.15 and @prisma/orm-postgres@8.0.0-rc.11. Any other prisma version fails the peer, so npm installs a full nested prisma@8.0.0-rc.15 (with @prisma/cli-engine 0.4.0) under @prisma/composer and @prisma/composer-cli. The prisma CLI's conformance check then fails on that nested engine. This reverts the dependency part of #348 and restores the pins it removed: alchemy 2.0.0-beta.78, effect 4.0.0-rc.115 and the exact @effect/* pins. beta.79 also lacks the peers, but its alchemy/Prisma entry fails to load without @alchemy.run/frontend-frameworks, and Composer imports alchemy/Prisma. beta.78 and beta.79 only work on effect rc.115, which still needs the @effect/vitest pin to keep npm on one effect copy. ORM 8.0.0-rc.17 and cli-engine 0.7.0 from #345 stay. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * chore(release): v0.29.1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> * docs(deps): one effect override placeholder, and name both pin sites in the dedupe check's timeout message Co-Authored-By: Claude Opus 5.5 <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 Opus 5.5 <noreply@anthropic.com>
2 participants
Moves Composer to Prisma ORM
8.0.0-rc.17and CLI engine0.7.0together. ORM rc.17 is the first ORM release that peers engine0.7.0, the engine the Prisma CLI ships since prisma/prisma-cli#337. With both on0.7.0, the CLI can drop the two temporary exceptions in its release check (prisma/prisma-cli#338).Changes
@prisma/cli-engine0.6.3→0.7.0in its five pins (the root override,@internal/cli, the prisma-cloud target, and@prisma/composer-cli's peer and dev dependencies). Engine0.7.0adds API and error codes and removes nothing.@prisma/orm-postgresand@prisma/orm-toolchain8.0.0-rc.16→8.0.0-rc.17in all seven manifests.foreign-keys-name-their-backing-index(and its extension twin): every contract is re-emitted with the rc.17 toolchain. Only the auth pack's contract changes. Its two foreign keys now name their backing indexes (account_userId_idx,session_userId_idx), so its storage hash moves.orm-collections-lock-rows,contract-artifacts-restamp: covered by the same re-emit. No other emitted file changes.enum-codecs-refusedandwith-is-a-collection-membermatch by pattern only: atimestamptz-stringcodec on a plain column, and an import attributewith: { type: 'json' }.0001_initis re-authored withmigration plan, as the pack'sprisma.config.tsdescribes. Its operations are the same; the rc.17 renderer writestimestamptzwithout quotes.examples/authre-materialises the auth space from the pack:0001_init,refs/head.json, and the snapshot directory move to the new hash.Storage hashes (old → new):
examples/auth:310f206d→0df0ef09No other storage, execution or profile hash changes.
For the release notes
An auth database deployed with an earlier Composer has its marker at
310f206d. Its next deploy stops withMIGRATION_PATH_NOT_FOUNDuntil someone runsprisma db signagainst it. The rc.17 extension guide prescribes the same re-sign for bundled contracts.Checks run locally
pnpm typecheck,lint,lint:casts,lint:deps(including the ORM-pin and contract-snapshot lints),test:scripts,check:skill-packaging,check:cli-engine-pin,check:publish-deps,check:orm-pins,check:npm-effect-resolution,check:family-static-graph,check:floor-importsandlint:retired-binary-namepass.turbo run test --continue: 64 of 66 tasks pass. The two failures come from this machine's shared local Postgres daemon, not from this change:local-target: itsbeforeAllhook timed out after 5 s while it started the daemon.integration-tests: the daemon reporteddatabase or disk is fulland a held lock file after the disk filled up mid-run, and it still held an orders database from an older run.