# prisma/release
Prisma v8.0.0-rc.15
importance: highbreakingmigrationfeatureprerelease
This release introduces significant changes to how SQL contracts store data types, enforces stricter type checking, and adds new features like middleware enhancements and query scopes. Breaking changes require careful migration steps, particularly around contract storage and column descriptors.
affected
Developers using SQL contracts, custom collections, or TypeScript contracts are affected by breaking changes and need to follow migration steps.
action
Follow the provided upgrade recipes and migration steps to ensure compatibility with this release.
release_signals
-SQL contract columns now store `dataType` (e.g., `pg/text`) instead of `nativeType` (e.g., `int4`). Upgrade requires running a script and signing databases.
-List cardinality in `contract.json` is now stored as an object (e.g., `many: { elementNullable: false }`).
-Codecs now enforce stricter type checking for contract values, including defaults and enums.
-`setDefault` in `migration.ts` now takes the column directly instead of SQL text.
-TypeScript contracts must explicitly list extensions whose codecs they use.
+Middleware gains an `afterTransaction` stage.
+Cache middleware gains invalidation support.
+Scopes allow sharing a piece of a query across models.
+Lists can now hold `null` elements.
migration_steps5 steps
- 01Run the `data-type-in-contract` script to upgrade contracts.
- 02Use `prisma db sign` to sign databases after upgrading.
- 03Re-emit MongoDB contracts and refresh their historical snapshots.
- 04Update `migration.ts` files to use `setDefault` with columns instead of SQL text.
- 05Ensure TypeScript contracts list all extensions whose codecs they use.
code_snippet
```json
"email": { "codecId": "pg/text@1", "dataType": "pg/text", "nullable": false }
```# 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.