The engine 0.6.1 transition is over: delete the conformance exceptions

[wmadden-electric]

At a glance

-      exceptions: [
-        { familyPackage: "@prisma/composer-cli",  familyPin: "0.4.0", shellPin: "0.6.1", … },
-        { familyPackage: "@prisma/composer-cli",  familyPin: "0.5.0", shellPin: "0.6.1", channel: "dev", … },
-        { familyPackage: "@prisma/orm-toolchain", familyPin: "0.4.0", shellPin: "0.6.1", … },
-      ],
+      exceptions: [],

The release checks in packages/cli/scripts/conformance.ts refuse to ship a prisma whose command families were built against a different engine than the one it ships. While engine 0.6.1 was new, the families could not peer it yet, so these three entries let that mismatch through. Both families have now released against 0.6.1:

Package	Version pinned in prisma 8.0.0-rc.17	Engine it peers
@prisma/composer-cli	0.23.0	0.6.1
@prisma/orm-toolchain	8.0.0-rc.12	0.6.1

So the entries now describe installs that no longer happen. They have to go: an entry left in place would let a real two-engine install through the next time those exact versions meet.

Checked

pnpm check:conformance reports "5 subject(s) checked, nothing to report" on both the release channel and the dev channel (PUBLISH_CHANNEL=dev), with the list empty. The dev builds (composer-cli@0.23.0-dev.1, orm-toolchain@8.0.0-rc.12-dev.13) also peer 0.6.1. pnpm lint and pnpm typecheck pass.

Also in this PR

The project ledger (.drive/projects/prisma-cli-v8/deferred.md) closes three entries that were no longer true:

• The engine transition "in flight" entry now records that the transitions through 0.6.1 are closed.
• The family path-resolution entry now records how it shipped: composer through composer#262, and the orm section through feat(config): the orm section is declared once as a schema, and the engine resolves its paths orm#30372's configSchema declaration, which superseded ORM config paths resolve against the file that declared them orm#30128. It also records a check run from the published prisma 8.0.0-rc.17: root and nested configs merge, paths resolve against the file that declares them, and prisma init in a subdirectory skips the root-level steps.
• The defineConfig rename entry is marked fixed by Config files import definePrismaConfig, the engine's current name for the marker orm#30129.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 57 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

This review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 20c5b22f-d383-41a5-b6cb-c4d0a8e41093

📥 Commits

Reviewing files that changed from the base of the PR and between a00dae7 and e3369f5.

📒 Files selected for processing (2)

• .drive/projects/prisma-cli-v8/deferred.md
• packages/cli/scripts/conformance.ts

---

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

npx https://pkg.pr.new/@prisma/cli@291

npx https://pkg.pr.new/@prisma/cli-engine@291

commit: e3369f5