Repository navigation
Release 8.0.0-rc.34: follow the products' released versions: @prisma/composer-cli 0.38.0 -> 0.39.0; @prisma/orm-toolchain 8.0.0-rc.23 -> 8.0.0-rc.24; @prisma/composer 0.38.0 -> 0.39.0 - #392
Merged
Conversation
…composer-cli 0.38.0 -> 0.39.0; @prisma/orm-toolchain 8.0.0-rc.23 -> 8.0.0-rc.24; @prisma/composer 0.38.0 -> 0.39.0 Opened automatically (update-product-versions.yml); merging releases the CLI. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
prisma-bot
enabled auto-merge (squash)
November 16, 2026 17:03
commit: |
SevInf
pushed a commit
that referenced
this pull request
Nov 16, 2026
…#393) ## Why #392 pinned `@prisma/orm-toolchain` 8.0.0-rc.24 and `@prisma/composer-cli` / `@prisma/composer` 0.39.0, which all peer `@prisma/cli-engine` 0.10.0. Two things followed from that: - The conformance exceptions that allowed the families to peer engine 0.9.0 met their `removeWhen` conditions and no longer apply. - The shell's tests covered only the Prisma 7 entries the shell declares itself. Nothing in this repo checked that the paths and flags declared by the ORM and Composer families settle as the v7 error in the built CLI. ## What changed - `packages/cli/tests/v7-inventory.test.ts` (new): builds the CLI with `buildCli()`, the same families the shipped binary mounts, from the installed released packages, and runs 37 cases in-process: - 24 command paths expected as `CLI.V7_COMMAND`: `bootstrap`, `version`, `debug`, `mcp`, `complete`, `platform status`, `postgres link`, `migrate dev|deploy|status|diff|reset|resolve`, `generate`, `validate`, `format`, `studio`, `db pull|push|seed|execute`, `dev ls|rm|start`. - 13 flags expected as `CLI.V7_FLAG`: `init --db|--no-skills|--datasource-provider|--generator-provider|--preview-feature|--output|--url|--with-model`, `dev --port|--db-port|--shadow-db-port|--debug`, `dev stop --debug`. - For each case it checks the code, exit 2, that `why` contains `npm install --save-dev @prisma/prisma7@7` and `prisma7 ` and does not mention `npx`, that there is at least one next action, that the human output contains every next action's command or URL from `--json`, and that every `run-command` next action names a mounted command whose `--help` exits 0 without `CLI.UNKNOWN_COMMAND` or a v7 error. It does not assert the families' exact `why` text, because each family tests its own wording. - `packages/cli/scripts/conformance.ts`: removes both engine-peer exceptions, leaving `exceptions: []`. - `docs/reference/error-reference.md` (`CLI.V7_COMMAND`): documents that the ORM's `migrate dev|deploy|status|reset|resolve` entries end with the conditional sentence "While Prisma 7 still owns this project's migrations, install its CLI with `npm install --save-dev @prisma/prisma7@7` and run `prisma7 <path>` instead." No command is mounted or changed, so no e2e test is owed. ## Testing - `pnpm typecheck`: passes - `pnpm lint`: passes - `pnpm check:error-reference`: passes - `pnpm --filter @prisma/cli test`: 71 files, 1222 passed, 1 skipped - `PUBLISH_CHANNEL=dev pnpm check:conformance`: "5 subject(s) checked, nothing to report". I ran this from a clone on a local ext4 filesystem. In the original worktree on a virtiofs mount, packing `prisma` fails in `scripts/stage-skills.mjs` because `cpSync` returns EACCES there. That failure comes from the environment and is unrelated to this change. - Spot-check: I temporarily changed the `db seed` case to `db sow`, a path that is not redirected. The test failed with `expected 'CLI.UNKNOWN_COMMAND' to be 'CLI.V7_COMMAND'`. After I reverted the change, all 37 cases passed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/composer-cli 0.38.0 -> 0.39.0; @prisma/orm-toolchain 8.0.0-rc.23 -> 8.0.0-rc.24; @prisma/composer 0.38.0 -> 0.39.0). Merging releases
prisma@8.0.0-rc.34underlatest; the checks on this pull request are what stand between a product release and that CLI release.