chore: scaffold with Composer 0.24.0 and prisma 8.0.0-rc.18

[kristof-siket]

At a glance

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

Package	Before	After
@prisma/composer	0.23.0	0.24.0
@prisma/composer-prisma-cloud	0.23.0	0.24.0
prisma	8.0.0-rc.17	8.0.0-rc.18

ORM pins (@prisma/orm-postgres / @prisma/orm-mongo) stay on 8.0.0-rc.12.

Why

Composer 0.24.0 includes the Windows assemble fix for EPERM / "operation not permitted" during prisma deploy (prisma/composer#319). New projects created with create-prisma were still installing Composer 0.23.0, so they kept hitting that failure even after the Composer release.

Deploy runs the project's local prisma binary. prisma@8.0.0-rc.17 depends on @prisma/composer-cli@0.23.0, so the CLI pin has to move with Composer. prisma@8.0.0-rc.18 depends on @prisma/composer-cli@0.24.0.

Why the ORM does not move

@prisma/composer-prisma-cloud@0.24.0 still peers @prisma/orm-postgres@8.0.0-rc.12 exactly. Pinning the ORM to 8.0.0-rc.13 (the toolchain that ships inside prisma@8.0.0-rc.18) makes npm install fail with ERESOLVE.

So this bump follows the install peer for the ORM, and the CLI's @prisma/composer-cli dependency for Composer. When composer-prisma-cloud peers rc.13, a follow-up can move the ORM pins together.

check:pins

bun run check:pins now verifies:

1. pinned @prisma/composer matches prisma's @prisma/composer-cli dependency
2. pinned ORM matches @prisma/composer-prisma-cloud's peerDependency

It warns (does not fail) when prisma's bundled @prisma/orm-toolchain differs from the ORM pin for the reason above.

Test plan

• bun run check:pins
• bun run test:unit
• bun run format / lint / typecheck
• CI green
• Manual: npm create prisma@<this-build> -- --template next --provider postgres on Windows, deploy, confirm assemble no longer fails with EPERM

[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: Essentials

Run ID: 046a56a3-b609-4a3e-a3ae-6d95e27e271d

📥 Commits

Reviewing files that changed from the base of the PR and between 3c9947f and 7afa218.

📒 Files selected for processing (3)

• scripts/check-pins.ts
• src/constants/dependencies.ts
• tests/dependencies.test.ts

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 3 reviews per hour.

---

Summary by CodeRabbit

• Updates
  • Composer tooling is now aligned on version 0.24.0, and Prisma is updated to version 8.0.0-rc.18.
  • Compatibility checks now verify that the Composer tools and cloud integration use matching versions. An optional ORM toolchain version mismatch is reported as a warning rather than blocking the check.

Walkthrough

The dependency pins change to @prisma/composer 0.24.0, @prisma/composer-prisma-cloud 0.24.0, and prisma 8.0.0-rc.18. The pin-check script validates matching Composer pins, Prisma’s Composer CLI dependency, and the cloud package’s Postgres ORM peer. A missing or mismatched Prisma ORM toolchain dependency no longer fails the check; a mismatch produces a warning when the dependency exists. Dependency tests expect the updated versions.

Priority: ➖ Normal

Merge Risk: ⚪ Minimal · up to 7afa2

The pin updates and checks are ready for normal validation; no concrete merge-blocking issue is established.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 3 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the primary changes: updating Composer to 0.24.0 and Prisma to 8.0.0-rc.18 for generated projects.
Description check	✅ Passed	The description directly explains the package version updates, pin constraints, validation changes, and test status.
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.

• Fix all pre-merge checks with AI

✨ 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.3-pr.118.385.1
• Tag: pr118
• Run with Bun: bunx create-prisma@pr118
• Run with npm: npx create-prisma@pr118
• Run with Yarn: yarn dlx create-prisma@pr118
• Run with pnpm: pnpm dlx create-prisma@pr118
• Run with Deno: deno run -A --minimum-dependency-age=0 npm:create-prisma@pr118
• Workflow run: https://github.com/prisma/create-prisma/actions/runs/36543983820