# prisma/release
Prisma v8.0.0-rc.17
importance: highbreakingmigrationfeatureprerelease
This release introduces significant changes to migrations, ensuring data loss is explicitly confirmed. The ORM client now supports row locks, and several API methods have been renamed for clarity. Enum handling has been updated to reflect database-stored values.
affected
Developers using Prisma for migrations and ORM operations are affected by these changes, particularly those handling enums and migrations.
action
Review and update migration scripts and ORM client code to align with the new API changes and enum handling.
release_signals
-`--confirm` no longer consents to data loss; explicit `--delete` or `--rename` is required.
-`destructive` operations now strictly mean data loss; other changes are classified as `widening`.
-Control API now uses a callback for answering questions, removing `consent` and `acceptDataLoss`.
-Collection methods `apply` and `scope` are renamed to `with` and `fragment`.
-Enum members must be written as the database stores them, affecting codecs and PSL enums.
+Migrations now ask for confirmation before data loss, with options to delete or rename data.
+ORM client gains row locks for better concurrency control.
+Enum members are now stored and returned as their database-stored values.
migration_steps3 steps
- 01Replace `--confirm` with `--delete` or `--rename` in migration scripts.
- 02Update collection method calls from `apply` to `with` and `scope` to `fragment`.
- 03Re-emit contracts and update enum handling to reflect database-stored values.
code_snippet
```ts
const postSummary = db.orm.public.Post.fragment((posts) => posts.select('id', 'title').include('user'));
const posts = await db.orm.public.Post.with(notDeleted).with(postSummary).all();
```# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.