v8.0.0-rc.8
Breaking Changes📦 prismaView on GitHub →
⚠ 1 breaking✨ 1 features🐛 4 fixes🔧 5 symbols
Summary
This release updates the toolchain to use `@prisma/cli-engine@0.3.0` and refines the `migration plan` command to prevent silent failures from empty databases when migrations exist. It also improves language server compatibility with Windows paths.
⚠️ Breaking Changes
- The engine peer moves to `@prisma/cli-engine@0.3.0`. `@prisma/orm-toolchain` now requires `@prisma/cli-engine` version 0.3.0 (up from 0.2.3). The `@prisma/management-api-sdk` is now a peer dependency (`^1.55.0`) of `@prisma/cli-engine`, supplied by the `prisma` CLI shell at runtime. If you pin the engine yourself and run it outside the CLI shell, you must update to 0.3.0 and install the SDK separately.
Migration Steps
- If you pin the engine yourself and run it outside the CLI shell, update to `@prisma/cli-engine@0.3.0` and install `@prisma/management-api-sdk` separately.
✨ New Features
- The `prisma-8` skill is now auto-installed by `prisma init` and teaches agents about the migration system's real model (plan-from-state with explicit baselines), preventing agents from producing full-create plans against real databases.
🐛 Bug Fixes
- `migration plan` now refuses to plan from an empty database when migrations already exist on disk, instead of silently producing a failing full-create package. A structured error is shown, and planning from baseline is available as an explicit opt-in.
- Structured errors' `docsUrl` links now correctly point to `docs.prisma.io/docs/orm/v8/...`.
- The language server now canonicalizes Windows file URIs, ensuring schema files with Windows paths are recognized.
- The `dev` dist-tag no longer becomes stale after a release; a `-dev.1` build is now published to `main` with each release, ensuring `@dev` installs always use the current release's engine pins.