v8.0.0-rc.1-dev.46
Breaking Changes📦 prismaView on GitHub →
⚠ 1 breaking✨ 2 features🐛 2 fixes🔧 4 symbols
Summary
The CLI engine is now an exact peer dependency of the toolchain, preventing version conflicts and improving installation reliability. Conformance checks have been updated to support bin-less packages and detect incorrect dependency placements.
⚠️ Breaking Changes
- The `@prisma/cli-engine` is now a `peerDependency` of `@prisma/orm-toolchain` instead of a regular `dependency`. This means that npm will fail installation if there are version conflicts, preventing multiple engine versions from being installed. Consumers of `@prisma/orm-toolchain` must ensure they have a compatible version of `@prisma/cli-engine` installed.
Migration Steps
- Ensure that your project has `@prisma/cli-engine` declared as a `peerDependency` with an exact version matching the expected engine version used by `@prisma/orm-toolchain`.
✨ New Features
- The CLI engine is now an exact peer dependency, ensuring only one version is present in the dependency tree and failing installation on conflicts.
- The conformance check now correctly handles packages without a `bin` entry by smoke testing the published `/cli` entry in a fresh Node.js environment, maintaining the anti-vacuity guarantee without requiring an executable that is no longer shipped.
🐛 Bug Fixes
- Resolved an issue where the conformance check would fail on `main` with 'the packed manifest has no bin entries' after the retirement of the `prisma-next` bin.
- Fixed an issue where `@prisma/orm-toolchain` could include a second, silent copy of the engine as an ordinary dependency, leading to version conflicts.