chore: create new projects with Prisma ORM 8.0.0-rc.13, prisma 8.0.0-rc.19 and Composer 0.25.0

[wmadden-electric]

At a glance

create-prisma writes exact package versions into every project it creates. This pull request changes five of them and keeps two:

Package	Before	After
@prisma/orm-postgres	8.0.0-rc.12	8.0.0-rc.13
@prisma/orm-mongo	8.0.0-rc.12	8.0.0-rc.13
prisma	8.0.0-rc.18	8.0.0-rc.19
@prisma/composer	0.24.0	0.25.0
@prisma/composer-prisma-cloud	0.24.0	0.25.0
alchemy	2.0.0-beta.78	unchanged
effect (override in the new project)	4.0.0-rc.115	unchanged

What this does

New projects now use Prisma ORM 8.0.0-rc.13, the prisma command-line tool 8.0.0-rc.19, and Prisma Composer 0.25.0. Each is the latest release on npm. No template changes.

Why the packages move together

Prisma Composer is the deploy tool that new projects install. Its package @prisma/composer-prisma-cloud declares @prisma/orm-postgres as a peer dependency with an exact version. Version 0.24.0 requires 8.0.0-rc.12, and version 0.25.0 requires 8.0.0-rc.13. So the ORM cannot move unless Composer moves too, or npm install fails with ERESOLVE.

The prisma package depends on an exact version of @prisma/composer-cli, which must equal the Composer version in the project. prisma 8.0.0-rc.18 depends on 0.24.0, and 8.0.0-rc.19 depends on 0.25.0. bun run check:pins checks both rules.

Until now the prisma package bundled the toolchain of ORM 8.0.0-rc.13 while new projects installed ORM 8.0.0-rc.12. After this change the two are the same release.

Composer 0.25.0 depends on alchemy 2.0.0-beta.78 and effect 4.0.0-rc.115, the same versions as Composer 0.24.0, so those two do not move. alchemy 2.0.0-beta.79 is on npm, but no Composer release depends on it.

Files changed

• src/constants/dependencies.ts holds the versions. The comment on the ORM version now states the rule without naming a version.
• tests/dependencies.test.ts expects the new versions.

Why the templates need no change

The templates do not contain a schema or generated contract files. prisma orm init and the installed toolchain write them when the project is created, so they always match the installed versions.

The upgrade instructions for 8.0.0-rc.13 ship inside @prisma/orm-postgres. A search of templates/ and src/ for the pattern of each entry found nothing: no code reads .ref.table or .ref.column, calls .default(...) with a literal, calls .cursor(...), builds a contract.source object, imports @prisma/orm-mongo/adapter/..., or uses the MongoDB migration runner. The MongoDB schema that prisma orm init writes uses only ObjectId and String, so the renamed MongoDB scalar types and the new Json rules do not apply.

Peer dependency warnings for @prisma/cli-engine

prisma 8.0.0-rc.19 depends on @prisma/cli-engine 0.6.2. @prisma/orm-toolchain 8.0.0-rc.13 and @prisma/composer-cli 0.25.0 declare @prisma/cli-engine 0.6.1 as a peer dependency. This produces a warning only. The install succeeded with all four package managers, and prisma orm init, prisma contract emit and prisma migration plan ran in each project.

Package manager	Result
npm 11.6.2	No warning. npm installs 0.6.1 for the two packages and 0.6.2 for prisma.
pnpm	Warning: unmet peer @prisma/cli-engine, installed 0.6.2, wanted 0.6.1.
Yarn 4.13.0	Warning: peer dependencies incorrectly met. Done with warnings.
bun 1.3.13	Warning: incorrect peer dependency "@prisma/cli-engine@0.6.2", twice.

This pull request adds no override for it. The fix belongs in the next releases of those two packages.

What was checked

• bun run check, bun run typecheck, bun run check:pins, bun run build, bun run test:unit (86 tests passed) and bun run test:e2e (12 tests passed).
• A project was created from the hono template with PostgreSQL and npm, and run against a PostgreSQL 17 container. prisma contract emit, prisma db migrate (1 migration, 6 operations) and prisma migration status (Up to date) passed. The build and the type check passed. The server returned the three sample users, and the table "User" held those three rows.
• A project was created from the hono template with MongoDB and npm. The install succeeded with the mongodb override from fix: new MongoDB projects install with npm instead of failing with ERESOLVE #116, and installed mongodb 7.7.0 only. prisma contract emit, the build and the type check passed.
• Projects were created from the hono template with PostgreSQL and each of pnpm, Yarn and bun, for the table above.

What this does not do

• Nothing was deployed. Every project was created with --no-deploy, so prisma deploy with Composer 0.25.0 is not checked here.
• The MongoDB project was not run against a database.
• The unit test renders Composer into every supported combination takes about 4 seconds against a limit of 5 seconds. It timed out in 3 of 7 local runs. It does not depend on the versions, and this pull request does not change it.

Agent: keen-finch-33
🤖 Generated with Claude Code

[coderabbitai]

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: Advanced

Run ID: 4531ee42-b3a1-46ae-b492-c340308b4e06

📥 Commits

Reviewing files that changed from the base of the PR and between b76b157 and e85fc3d.

📒 Files selected for processing (2)

• src/constants/dependencies.ts
• tests/dependencies.test.ts

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Summary by CodeRabbit

• Updates
  • Updated the Prisma tooling versions used by the product, including Composer, the MongoDB and PostgreSQL ORM packages, and the Prisma CLI.
  • The PostgreSQL ORM version requirement remains tied to the exact peer-dependency version required by the cloud Composer package; using a newer ORM toolchain does not change that compatibility requirement.

Walkthrough

The dependency map updates the Composer packages to 0.25.0, the Prisma ORM packages to 8.0.0-rc.13, and Prisma CLI to 8.0.0-rc.19. The PostgreSQL peer-dependency comment now states that its version must exactly match the cloud Composer peer dependency. The dependency test expectations are updated to match these versions.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to e85fc

The updated package pins align with their release requirements, and the dependency test covers each changed version. No identified issue prevents merging.

Architecture Summary

Architecture risk: 🔵 Low · up to e85fc

The change affects 2 systems.

Changed systems: src, tests

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — src (service) was modified; 1 changed file maps to changed impact.
• observed — tests (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in src/constants/dependencies.ts: dependencyVersionMap updates the two composer packages to 0.25.0 and both ORM packages to 8.0.0-rc.13; the postgres comment now requires an exact match with the cloud composer peer dependency even when Prisma bundles a newer toolchain. The previous comment described remaining on rc.12 until the peer changed.
• observed — Modified behavior in src/constants/dependencies.ts: The pinned prisma version changes from 8.0.0-rc.18 to 8.0.0-rc.19.
• observed — Modified behavior in tests/dependencies.test.ts: Updated the expected versions for both Prisma ORM packages from 8.0.0-rc.12 to 8.0.0-rc.13, both Composer packages from 0.24.0 to 0.25.0, and Prisma CLI from 8.0.0-rc.18 to 8.0.0-rc.19.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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 2…
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.
Title check	✅ Passed	The title clearly summarizes the primary change: new projects will use Prisma ORM 8.0.0-rc.13, prisma 8.0.0-rc.19, and Composer 0.25.0.
Description check	✅ Passed	The description directly explains the dependency updates, version alignment, unchanged packages, validation results, and known testing limits.

✨ 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.}

[github-actions]

PR preview published

• Version: 0.13.4-pr.121.391.1
• Tag: pr121
• Run with Bun: bunx create-prisma@pr121
• Run with npm: npx create-prisma@pr121
• Run with Yarn: yarn dlx create-prisma@pr121
• Run with pnpm: pnpm dlx create-prisma@pr121
• Run with Deno: deno run -A --minimum-dependency-age=0 npm:create-prisma@pr121
• Workflow run: https://github.com/prisma/create-prisma/actions/runs/36565068914