chore: create new projects with Prisma ORM 8.0.0-rc.12, prisma 8.0.0-rc.17 and Composer 0.23.0

[wmadden-electric]

At a glance

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

Package	Before	After
@prisma/orm-postgres	8.0.0-rc.11	8.0.0-rc.12
@prisma/orm-mongo	8.0.0-rc.11	8.0.0-rc.12
prisma	8.0.0-rc.15	8.0.0-rc.17
@prisma/composer	0.20.0	0.23.0
@prisma/composer-prisma-cloud	0.20.0	0.23.0
alchemy	2.0.0-beta.74	2.0.0-beta.78
effect (override in the new project)	4.0.0-rc.112	4.0.0-rc.115

What this does

New projects now use Prisma ORM 8.0.0-rc.12, the prisma command-line tool 8.0.0-rc.17, and Prisma Composer 0.23.0. No template code changes, apart from the effect version. The change shipped in create-prisma 0.13.3.

Why

The Prisma documentation describes Prisma ORM 8.0.0-rc.12. In that release, a model User in the Prisma schema that has no @@map attribute creates the table "User". In 8.0.0-rc.11 it created the table "user". A project created by create-prisma 0.13.2 used 8.0.0-rc.11, so it did not behave as the documentation says.

The old versions also blocked an upgrade. In a project created by 0.13.2, npm install -D prisma@latest failed with ERESOLVE, because the exact versions in the project did not accept the newer prisma package.

Why the other packages move

The prisma package bundles a toolchain that is tested against one ORM release only, so it moves together with the ORM packages. bun run check:pins checks that the two match.

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.20.0 requires 8.0.0-rc.11, and so does 0.22.0. Version 0.23.0 requires 8.0.0-rc.12. So the ORM cannot move unless Composer moves too.

alchemy 2.0.0-beta.78 and effect 4.0.0-rc.115 are the exact versions that Composer 0.23.0 depends on. New projects also force a single effect version through an override, so that override changes in templates/create/_package-manager/pnpm-workspace.yaml.hbs as well.

Files changed

• src/constants/dependencies.ts holds the versions.
• templates/create/_package-manager/pnpm-workspace.yaml.hbs holds the effect override.
• Three test files expect the new versions.

Why the templates need no other change

8.0.0-rc.12 changes more than table names. The templates do not use any of the changed features:

• They contain no raw SQL. No template or script runs migration new, reads a MIGRATION.* error code, calls .defaultSql(...), or calls prepare(...).
• templates/create/_shared/prisma.config.ts.hbs already imports definePrismaConfig.
• 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.

What was checked

• Continuous integration passed on this pull request, including the job that creates a project on Windows.
• Locally: 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 (11 tests passed).
• A project was created from the minimal template with PostgreSQL and npm, and run against a PostgreSQL 17 container. prisma contract emit, prisma db migrate (1 migration, 6 operations), prisma migration status and prisma db verify all passed. The server returned the three sample users from the table "User". npm install -D prisma@latest succeeded in that project.
• A project was created from the minimal template with MongoDB and bun. It passed the type check.

What this does not do

Creating a MongoDB project with npm fails with ERESOLVE. alchemy declares an optional peer dependency mongodb@^6.10.0, and @prisma/orm-mongo requires mongodb@^7.0.0. The same failure happens with the versions from before this pull request, so this pull request does not cause it and does not fix it. Issue #114 tracks it, and #116 proposes a fix.

🤖 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: b69e6131-72c0-4f96-a898-9515df11137f

📥 Commits

Reviewing files that changed from the base of the PR and between e9a7047 and 345fe7d.

📒 Files selected for processing (5)

• src/constants/dependencies.ts
• templates/create/_package-manager/pnpm-workspace.yaml.hbs
• tests/dependencies.test.ts
• tests/e2e/create-prisma.e2e.test.ts
• tests/install.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

• Maintenance
  • Updated the versions of Prisma, its Composer and ORM packages, Alchemy, and Effect used in generated projects.

Walkthrough

Dependency pins were updated for the Prisma Composer packages, Prisma ORM packages, Alchemy, Effect, and Prisma CLI. The pnpm workspace Effect override was also updated. Dependency, end-to-end, and install tests now expect the corresponding versions.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 345fe

The PR updates scaffold dependency pins and matching expectations. The inspected package requirements align, with no new install incompatibility evident; it is ready for normal checks.

Architecture Summary

Architecture risk: 🔵 Low · up to 345fe

The change affects 3 systems.

Changed systems: src, tests, templates

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; 3 changed files map to changed impact.
• observed — templates (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in src/constants/dependencies.ts: Updated the pinned versions of the Prisma composer packages, MongoDB and PostgreSQL ORM packages, Alchemy, Effect, and Prisma CLI; the PostgreSQL peer-dependency note remains unchanged.
• observed — Modified behavior in templates/create/_package-manager/pnpm-workspace.yaml.hbs: The effect override changes from 4.0.0-rc.112 to 4.0.0-rc.115.
• observed — Modified behavior in tests/dependencies.test.ts: Updated expected versions for the two Prisma ORM packages, both Composer packages, Prisma CLI, Alchemy, and Effect.
• observed — Modified behavior in tests/e2e/create-prisma.e2e.test.ts: The test expectation for packageJson.overrides.effect changes from 4.0.0-rc.112 to 4.0.0-rc.115.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the primary scaffold version updates, including Composer, Prisma ORM, and Prisma.
Description check	✅ Passed	The description directly explains the dependency updates, template change, compatibility rationale, validation steps, and known unchanged limitation.
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 4…
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.}

[github-actions]

PR preview published

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