v0.17.0

⚠️ Breaking Changes

• One `@prisma` package per application: The `@prisma-next/*` scope is retired. Applications should now depend on exactly one database facade (e.g., `@prisma/orm-postgres`) and any extension packs. Regenerating your contract will rewrite generated imports to facade entrypoints. See the [0.16-to-0.17 upgrade recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/upgrade/prisma-next-upgrade/upgrades/0.16-to-0.17/) and the [extension-author recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/extension-author/prisma-8-extension-upgrade/upgrades/0.16-to-0.17/).
• Every published error is a structured envelope with a dotted code: Legacy error systems are consolidated into a single scheme with `NAMESPACE.SUBCODE` codes, recognized by the `isStructuredError` type predicate instead of `instanceof`. Legacy error classes like `PslFormatError` are deleted. Prisma 7's `P1001`-style codes are not carried over. Example: `if (error instanceof PslFormatError)` becomes `if (isStructuredError(error) && error.code === 'PSL.PARSE_FAILED')`.
• Content hashes are bare hex: The `sha256:` prefix is removed from all content hashes. Loaders will reject the prefixed form. A codemod in the [0.16-to-0.17 recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/upgrade/prisma-next-upgrade/upgrades/0.16-to-0.17/) converts migration trees.
• Migration contract snapshots move into a content-addressed store: Per-migration sibling snapshot files are replaced by a single `migrations/snapshots/<hex>/` store. A one-shot migrator (`scripts/migrate-migrations-layout.mjs`) converts existing trees.
• PostgreSQL native types are authored in type position; the `@db.*` attribute channel is removed: Write native types directly (e.g., `VarChar(255)`, `Uuid`) instead of using `@db.*` attributes. `Json` now binds to native `json` storage, and `Jsonb` is a new scalar for jsonb. Example: `model User { id String @id @db.Uuid }` becomes `model User { id Uuid @id }`.
• Relation-loading and aggregates are lossless: Values read through `.include()` no longer pass through lossy Aggregate result types change: `count()` is a `bigint`, and decimal sums are strings. Regenerate your contract after upgrading.
• SQL indexes and RLS policies are name-identified: Every index and RLS policy has an exact name in the contract, which can be adopted by exact name (`@@map`).
• `extensionPacks` config key renamed to `extensions`: In `prisma-next.config.ts`, the TS builder, client options, and the emitted contract's top-level key have been renamed. The old key fails loudly. Contract hashes will change, requiring re-emission and re-anchoring of migrations. `contract.source.sourceFormat` is now `format`, and the facade `defineConfig` option `outputPath` is now `output`.
• Count-only mutation terminals renamed: `createCount(...)`, `updateCount(...)`, and `deleteCount()` are now `createAndCount(...)`, `updateAndCount(...)`, and `deleteAndCount()`. Behavior and results are unchanged.