v8.0.0-rc.1-dev.39
Breaking Changes📦 prismaView on GitHub →
⚠ 2 breaking✨ 4 features🔧 5 symbols
Summary
The `migration plan`, `migration new`, and `migration status` commands have been migrated to the new engine-based CLI. Retired `migration status` flags are now redirects to their new locations.
⚠️ Breaking Changes
- The `--legend` flag no longer errors when used with `--json` or `--quiet`. It is now silently ignored in these modes.
- Glyph auto-detection for tree commands is removed. Unicode glyphs are drawn by default; use `--ascii` to force ASCII output.
Migration Steps
- To use the functionality of `migration status --graph`, use `prisma-next migration graph` instead.
- To use the functionality of `migration status --all` or `migration status --limit`, use `prisma-next migration log --db <url>` instead.
- To use the functionality of `migration status --ref`, use `prisma-next migration status --to <contract>` instead.
✨ New Features
- `migration plan`, `migration new`, and `migration status` commands are now ported to the new engine-based CLI.
- Retired `migration status` flags (`--graph`, `--all`, `--limit`, `--ref`) are now redirects to new commands or flags.
- `migration status` now reports specific conditions like `CONTRACT.UNREADABLE`, `MIGRATION.MARKER_NOT_IN_HISTORY`, and `MIGRATION.MISSING_INVARIANTS` as warnings (severity 'warn') on a successful exit code (0), rather than errors.
- The CLI now uses a typed result protocol, with each run ending in a result envelope carrying an exit code, optional diagnostics, and typed next actions.