chore: scaffold with Composer 0.19.0 and Prisma ORM 8.0.0-rc.10 - #97
Conversation
Also removes the Deno primer under its rc.10 name (prisma-8.md) as well as the old prisma-next.md, and points the e2e expectations at the new header and primer name. 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>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Essentials Run ID: 📒 Files selected for processing (4)
Knowledge base: Disabled due to Summary by CodeRabbit
WalkthroughThe dependency map and dependency tests now use Composer ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
|
The Windows creation smoke failure ( |
PR preview published
|
@prisma/composerand@prisma/composer-prisma-cloud0.17.0 → 0.19.0;@prisma/orm-postgresand@prisma/orm-mongo8.0.0-rc.8 → 8.0.0-rc.10 (matches composer-prisma-cloud's exact peer).orm initwrites fromprisma-next.mdtoprisma-8.md. The Deno cleanup now removes either name, so Deno scaffolds stop keeping the primer onceprisma@latestis 8.0.0-rc.14.// use prisma-8header and expectsprisma-8.md.Unit tests, typecheck, and lint pass. Merge after
prisma@8.0.0-rc.14is on npm (prisma/prisma-cli), because scaffolds installprisma@latestand rc.13 still carries the rc.8 toolchain.🤖 Generated with Claude Code