This prerelease adds MySQL ORM writes, named MongoDB index handling, and convenience database types, while improving extension-pack discovery for PostgreSQL extensions. It also changes runtime validation and extension requirements in ways that may require application and extension updates; the release notes provide upgrade recipes and specific migration steps.
affected
Prisma 8 application and extension authors—especially MongoDB users and projects composing PostgreSQL extension packs—may need contract, API, and input-validation updates.
action
Use the matching app or extension upgrade recipe for this prerelease and perform the documented contract-emission and migration steps.
release_signals
-MongoDB indexes must carry names in contracts and migrations; duplicate inferred names are refused. Extension APIs for MongoDB indexes and index operations now require names.
-`prisma6Schema()` preserves Prisma 6 index-reading behavior, including refusing certain duplicate indexes and retaining some indexes that produce a new storage hash.
-PostgreSQL extension packs declare extensions in the unbound namespace; applications may not separately declare an extension already declared by a composed pack.
-`mongo()` and `mongoStatic()` require the extension packs used by the contract, and MongoDB `contract.json` must include `target`.
-`supabase()` and `postgres()` validate database inputs immediately; invalid, conflicting, or null inputs now fail, and Supabase no longer accepts `pg.Client`.
!The extension APIs `mongoStandardCodecs` and `buildStandardCodecRegistry` are removed.
+
migration_steps5 steps
01Follow the release's app or extension upgrade recipe for the applicable changes.
02After upgrading, run `prisma contract emit` once to restamp extension-generated contracts with the installed package version.
03For MongoDB indexes, emit the contract, run the script supplied by the app recipe to name indexes in migration snapshots, then run `prisma db sign` or plan a migration; name any indexes that would otherwise collide.
04For pgvector, PostGIS, ParadeDB, or citext packs, remove the application's duplicate extension declaration, run `prisma contract emit`, then run `prisma db migrate` to apply the pack migration without changing the database.
05For MongoDB projects composing extension packs, pass each pack's runtime descriptor to `mongo({ extensions })` and `mongoStatic({ extensions })`; ensure MongoDB contract JSON includes `target`.
This prerelease introduces PostgreSQL convenience date/time types and `Duration`, moves value objects into the storage plane, and adds PostgreSQL checks for value-object and discriminator columns. It also changes MongoDB APIs to use execution contexts and stack-created drivers, adds contract-declared PostgreSQL extensions, and broadens Prisma 7 and MySQL read support.
affected
Applications and extensions upgrading from v8.0.0-rc.21 are affected, especially those using PostgreSQL date/time types or value objects and MongoDB query, runtime, or driver APIs.
action
Because this is a prerelease with multiple breaking changes, follow the linked app or extension upgrade recipe before upgrading, and restamp contracts with `prisma contract emit`.
This prerelease adds enum-value rename and deletion planning for Postgres and SQLite, introduces public MySQL migration packages, and unifies MongoDB contract processing across TypeScript, PSL, and Prisma 6 sources. It also changes client error behavior and several contract APIs, with upgrade recipes documenting breaking changes and required follow-up steps.
affected
Applications and extensions upgrading to this prerelease may need code and contract updates, especially if they use MongoDB contract APIs, enum migrations, or synchronous error handling.
action
Use the rc.20-to-rc.21 app or extension upgrade recipe and run `prisma contract emit` after upgrading.
release_signals
-Client members that return promises or results now report closed-client, connection, or ended-transaction failures through the returned promise or result instead of throwing at the call; callers relying on synchronous `try`/`catch` must await the operation.
This release introduces significant breaking changes, including changes to JSON output formatting, contract storage, SQL builder inserts, MongoDB enum syntax, and Supabase role operations. It also adds new features like enhanced type alias support and improved Postgres migrations.
affected
Users relying on piped JSON output, type aliases in contracts, SQL builder inserts, MongoDB enum syntax, or Supabase role operations are affected.
action
Follow the provided upgrade recipes and apply the necessary changes to your codebase.
release_signals
-A piped ORM command prints data lines, not JSON, unless you pass `--json`. Requires `@prisma/cli-engine` 0.9.0. Scripts reading JSON from `prisma` commands must add `--json` flag.
This release introduces significant changes to how client generators, defaults, and contracts are handled, requiring schema and client code updates. Key changes include moving client generators to `@onCreate` and `@onUpdate`, removing `@noCheck`, and ensuring type-constructor arguments are values.
affected
Users of Prisma ORM with custom client generators, date/time defaults, or `@noCheck` annotations are affected and need to update their schemas and client code.
action
Follow the provided upgrade recipes and scripts to update your schemas and client code to match the new syntax and requirements.
release_signals
-Client generators are now written as `@onCreate(...)` and `@onUpdate(...)`, and `@default` means a database default. Existing `@default(uuid())`, `@default(cuid(2))`, `@default(ulid())`, and `@default(nanoid())` will be refused. Use `@onCreate(uuid())` and similar instead.
This release introduces significant changes to raw SQL handling, middleware hooks, full-text indexing, and polymorphic models. It also includes breaking changes that require careful migration.
affected
Developers using raw SQL in contracts, middleware hooks, full-text indexing, polymorphic models, or SQL ORM client field names are affected.
action
Follow the provided migration recipes and update your codebase to accommodate the breaking changes.
release_signals
-Raw SQL in a contract is a `sql` literal. Quoted strings are refused, and a script is provided to rewrite `.prisma` files.
-Middleware hooks are now activity hooks, with renamed methods and context changes.
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.
This release updates the toolchain to `@prisma/cli-engine` 0.6.3, resolving issues with Bun installations and improving `@default` diagnostics. It also introduces breaking changes for extension authors and fixes a contract validation issue.
affected
Developers using `@prisma/cli-engine` or extensions relying on `dataTypeLookup` and `dataTypeEntries` are affected.
action
Update `@prisma/cli-engine` to version 0.6.3 and follow the provided migration recipes.
release_signals
-The toolchain now requires `@prisma/cli-engine` 0.6.3, and projects or extensions pinning `@prisma/cli-engine` must update from `0.6.2` to `0.6.3`.
-`@default` diagnostics now point at the written value and provide clearer error messages.
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.
This release introduces several breaking changes, including updates to the serverless client's `connect()` method, canonical storage of date/time defaults, and stricter type checks in the Mongo ORM. New features enhance compatibility with `postgres()` clients and Node 24.
affected
Users of the serverless client, Mongo ORM, and those with date/time defaults in their schemas are affected by breaking changes.
action
Follow the provided upgrade recipes for detailed migration steps.
release_signals
-Serverless `connect()` returns a connection, not a `Runtime`. Replace `runtime.query(plan)` with `db.runtime().query(plan)`, and pass `db.runtime()` wherever the `connect()` result was used as a runtime.
This release enhances MongoDB compatibility with Postgres, introduces new features like `prisma contract print`, and enforces stricter type handling in TypeScript contracts. It also includes several breaking changes related to contract defaults, cursor ordering, and Mongo codec paths.
affected
Developers using MongoDB, TypeScript contracts, or custom contract configurations are affected by these changes.
action
Follow the provided upgrade recipes and migration steps to ensure compatibility with this release.
release_signals
-Generated defaults in the contract now use `ref: { namespace, entry, field }` instead of `ref: { namespace, table, column }`.
This release introduces significant changes including Postgres full-text search, prepared ORM reads, and schema file splitting. It also includes several breaking changes requiring careful migration.
affected
Projects using Prisma ORM, especially those with custom configurations or relying on `dbgenerated` defaults, are affected by these changes.
action
Follow the provided upgrade recipes for detailed migration steps.
release_signals
-Engine peer moves to `@prisma/cli-engine@0.6.1`, requiring `definePrismaConfig` instead of `defineConfig`.
This release updates the toolchain to `@prisma/cli-engine@0.4.0`, introducing Markdown output format for CLI commands. No other changes were made since rc.10.
affected
Projects pinning `@prisma/cli-engine` must update their pin to `0.4.0`.
action
Update the engine pin to `@prisma/cli-engine@0.4.0` if your project pins it directly.
release_signals
-The engine peer dependency has been updated to `@prisma/cli-engine@0.4.0`. Projects pinning the engine must update their pin to `0.4.0`.
+Added Markdown output format (`--format markdown`) to every CLI command.
This release completes the rename from Prisma Next to Prisma 8, introduces named model and result types, and adds attribute completion to the language server. It includes breaking changes for environment variables and contract types.
affected
Users relying on `PRISMA_NEXT_*` environment variables or needing to update contract types for to-one relations are affected.
action
Update environment variables and run `prisma contract emit` to ensure compatibility with the new contract format.
release_signals
-CLI environment variables lose the `NEXT_` infix. Rename `PRISMA_NEXT_*` to `PRISMA_*` in shell profiles, `.env` files, and CI.
This release candidate introduces stricter schema validation, reusable query-filter types, and fixes for language-server diagnostics and PostgreSQL migration verification. It includes several breaking changes, particularly around MongoDB schema handling and SQL ORM filter types.
affected
Developers using PostgreSQL enums, MongoDB schemas, or SQL ORM filter types are affected by the breaking changes and need to update their schemas and code accordingly.
action
Review and apply the provided upgrade recipes to migrate schemas and code to be compatible with this release.
release_signals
-Text-backed enum ordering in PostgreSQL now follows stored values, requiring explicit ranking expressions or numeric enum values for semantic ranking.
This release introduces breaking changes to the engine peer dependency and improves the migration system. It also includes several fixes related to migration planning, structured errors, and language server behavior.
affected
Users relying on the engine peer dependency or migration planning from an empty database are affected.
action
Upgrade to v8.0.0-rc.8 and follow the provided migration steps if necessary.
release_signals
-The engine peer dependency moves to `@prisma/cli-engine@0.3.0`, requiring `@prisma/management-api-sdk` as a peer dependency. Hosts pinning the engine must upgrade and install the SDK if running outside the CLI shell.
7.10.0highmigrationfeaturesecurityAug 25, 2026
7.10.0
This release introduces a compatibility package for running Prisma 7 alongside Prisma 8, enhances Prisma Studio's security, and includes fixes across Prisma Client and various database adapters.
affected
Users running Prisma 7 alongside Prisma 8 or using Prisma Studio are affected.
action
Install `@prisma/prisma7` and `@prisma/client` to run Prisma 7 alongside Prisma 8.
release_signals
!Prisma Studio's local HTTP server now binds to `127.0.0.1` and rejects non-local requests.
!Rejects browser requests from origins other than `localhost` or `127.0.0.1`.
This release introduces breaking changes to ORM pagination, renaming `take`/`skip` to `limit`/`offset`. It also updates the engine peer dependency to `@prisma/cli-engine@0.2.3`.
affected
Users relying on `.take(n)` and `.skip(n)` for ORM pagination or manually pinning the engine peer dependency are affected.
action
Update ORM queries to use `.limit(n)` and `.offset(n)` and ensure the engine peer dependency is set to `@prisma/cli-engine@0.2.3`.
release_signals
-ORM pagination methods `.take(n)` and `.skip(n)` are renamed to `.limit(n)` and `.offset(n)` for SQL and Mongo ORM collections. The old names are removed, but semantics remain unchanged.
-The engine peer dependency is updated to `@prisma/cli-engine@0.2.3`. Hosts pinning the engine must upgrade to this version.
This release introduces breaking changes for PostgreSQL temporal columns and agent skills setup, while adding the prisma-8 skill to npm tarballs.
affected
Users of PostgreSQL temporal columns and those relying on `prisma orm init` for agent skills setup are affected.
action
Follow the migration recipe for PostgreSQL temporal columns and update to `@prisma/cli-engine@0.2.2`.
release_signals
-PostgreSQL temporal columns now use explicit `Temporal` or text representations instead of `Date`. Users must choose a representation per column and re-emit contracts.
-
MySQL now supports ORM writes.
+PostgreSQL scalar types gain convenience types; SQLite and MySQL gain convenience date and time types.
+`mongo()` accepts extension packs, and `supabase()` accepts the options supported by `postgres()`.
+PostgreSQL extension packs locate extensions through the connection search path, supporting setups such as Supabase.
+Prisma ORM no longer refuses to start when loaded from more than one copy.
-
PostgreSQL `DateTime`, `Date`, and `Time` now use convenience defaults and read JavaScript `Date` or strings instead of `Temporal` values; use `TimestamptzTemporal`, `DateTemporal`, or `TimeTemporal` to retain the prior behavior. `temporal.CreatedAt` and `temporal.UpdatedAt` now use the new `DateTime`, and their `String` and `JsDate` variants are removed.
-Value objects move from the domain plane to `storage.namespaces.<ns>.entries.valueObject`; changing one is a migration, and contracts that retain the old `valueObjects` location are rejected. PostgreSQL migrations add checks and fail if existing rows violate them.
-MongoDB query, raw, ORM, and runtime APIs now take an execution context; several old enum helpers and runtime options are removed, and driver creation uses a runtime descriptor on the execution stack.
-`createMongoDriver` and `MongoDriverImpl` are no longer exported; extension-facing driver and SQL execution-stack types also change.
-PostgreSQL `contract infer`/`contract print` now emit convenience types; re-inferred `timestamptz` fields default to JavaScript `Date` and lose microseconds unless configured to preserve a string and precision.
!Removed `temporal.CreatedAt.String`, `temporal.CreatedAt.JsDate`, `temporal.UpdatedAt.String`, and `temporal.UpdatedAt.JsDate` variants.
!Removed MongoDB exports `createMongoDriver` and `MongoDriverImpl`, as well as `buildMongoEnums`, `MongoEnumAccessors`, `MongoOrmEnums`, and `ORM.MUTATION_DEFAULTS_MISSING`.
+PostgreSQL contracts can declare required extensions, including pgvector, PostGIS, ParadeDB, and the new citext pack.
+Adds PostgreSQL `Duration` and convenience `DateTime`, `Date`, and `Time` types with configurable storage, precision, and read representation.
+MongoDB clients create their driver from the execution stack; `connect()` can safely be called again.
+Prisma 7 reader now supports every PostgreSQL `@db.*` type Prisma 7 accepts; MySQL gains ORM and SQL builder reads.
+PostgreSQL derives checks for value-object and discriminator columns on managed tables.
migration_steps6 steps
01Follow the linked app or extension upgrade recipe for the 8.0.0-rc.21-to-8.0.0-rc.22 upgrade; the app recipe specifies step order.
02After upgrading, run `prisma contract emit` once to restamp contracts with the installed package version.
03To preserve prior PostgreSQL Temporal behavior, rename fields to `TimestamptzTemporal`, `DateTemporal`, or `TimeTemporal` (and use the corresponding TypeScript helpers).
04For value objects, run the app recipe's script to rewrite contracts, snapshots, and migrations, then sign each database before re-emitting.
05After re-emitting a contract read by `prisma7Schema(...)`, run `prisma db sign`; for inferred `timestamptz` fields that must retain string values and microseconds, use `DateTime(as: string, precision: 6)`.
06For MongoDB, replace `{ contract }` query/raw setup with a context from `mongoStatic({ contract })` or `mongo({ contract })`, and use the runtime driver descriptor on the execution stack.
-Removed enum values on Postgres and SQLite now require a rename or delete decision; non-interactive runs fail with `CLI.CONSENT_REQUIRED` unless given `--rename` or `--delete`.
-MongoDB contract APIs change: `mongoContract` requires `options.target`, `ContractDefinition` is renamed to `ContractInput`, and `MongoModelDefinition` is removed in favor of `ContractModel<MongoModelStorage>`.
-MongoDB contract sources now enforce consistent validation rules, so some formerly accepted contracts are refused; Prisma 6 schemas with duplicate identical indexes are merged, changing their storage hash.
-Calling `close()` with a supplied PostgreSQL pool or client now also closes the Prisma client's runtime, though the supplied pool or client remains open; SQLite file-open failures are now `SqlConnectionError` rather than `SqlQueryError`.
-Field presets are removed; equivalent contracts must be expressed using a type constructor or type alias.
+`migration plan` and `db update` can rename or delete removed enum values on Postgres and SQLite while rewriting affected rows.
+Public MySQL packages can plan and apply migrations.
+MongoDB contracts written in TypeScript, PSL, or Prisma 6 now build through one builder and follow consistent rules.
+PostgreSQL date/time types identify the kind of value they read, and text date/time types parse ISO 8601 on every server.
+`db migrate` explains when a database contract is outside the migration graph and offers recovery options that do not reset the database.
migration_steps5 steps
01Follow the app or extension upgrade recipe for rc.20 to rc.21; the release also notes that the rc.18 and rc.19 upgrade guides have been fixed.
02After upgrading, run `prisma contract emit` once so extension-stamped contracts match the installed package version.
03For non-interactive enum removal or value changes, provide `--rename Status.ARCHIVED:Status.RETIRED` or `--delete Status.ARCHIVED` as appropriate.
04Update MongoDB code to pass a target pack to `mongoContract`, use `ContractInput`, and replace `MongoModelDefinition` with `ContractModel<MongoModelStorage>`.
05For Prisma 6 schemas whose duplicate indexes are merged, run `prisma contract emit` and then `prisma db sign`.
The contract now stores a column's type directly, not the type alias it was written with. Requires rewriting stored contracts and migration snapshots, and re-emitting contracts.
-SQL builder inserts must include every column the database requires. Missing non-nullable columns without defaults now cause type errors.
-MongoDB enum members and discriminator values must be written in the syntax of their data type. Quoted members on non-text types are refused.
-Supabase role operations now require `forRole(binding)` and have updated `pg` option handling.
+Type aliases in PSL can now set `@default`, `@onCreate`, and `@onUpdate`.
+Postgres migrations can now rename, move, and remove namespaces, and change relation actions or primary keys.
+Failed migration checks now name the expected object.
migration_steps5 steps
01Add `--json` to scripts reading JSON from `prisma` commands.
02Run the app recipe's script to rewrite stored contracts and migration snapshots, then re-emit contracts.
03Ensure SQL builder inserts include all required columns.
04Update MongoDB enum members to use correct syntax for their data types.
05Update Supabase role operations to use `forRole(binding)`.
-Clients now take the contract as a typed value. The `contractJson` option and type argument on client calls are removed. Use `contractFromJson<Contract>(contractJson)` from the facade's `/static` entry and pass `{ contract }`.
-Date, time, interval, and bytes defaults are now written with tags, and each default has one stored form. Quoted defaults for these types are refused, and values must match the column's type.
-`@noCheck` is removed. Lists that allow null elements are now written as `T?[]`. Contracts with `noCheck` keys will no longer load.
-Type-constructor arguments are now values. Quoted numbers in type constructors like `VarChar("255")` are refused; write the number without quotes.
+Client generators are now explicitly marked with `@onCreate(...)` and `@onUpdate(...)`.
+Clients take the contract as a typed value, improving type safety.
+Date, time, interval, and bytes defaults are now written with tags for clarity and consistency.
+Lists that allow null elements are now written as `T?[]`.
+Type-constructor arguments are now values, ensuring better type checking.
migration_steps5 steps
01Run the provided upgrade scripts to rewrite your Prisma 8 schema files.
02Update client code to use `contractFromJson<Contract>(contractJson)` and pass the contract as a typed value.
03Replace `@default(uuid())` with `@onCreate(uuid())` and similar for other client-generated defaults.
04Replace `T[] @noCheck(elementNotNull)` with `T?[]` and remove `@noCheck(membership)`.
05Ensure type-constructor arguments are unquoted values, e.g., `VarChar(255)` instead of `VarChar("255")`.
Extension authors must update their code to use `dataTypes` instead of `dataTypeLookup` and `dataTypeEntries`, with changes to `ControlStack`, `ContractSourceContext`, and other related components.
migration_steps2 steps
01Follow the [app recipe](https://github.com/prisma/orm/blob/v8.0.0-rc.16/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.15-to-8.0.0-rc.16/) for upgrading applications.
02Follow the [extension recipe](https://github.com/prisma/orm/blob/v8.0.0-rc.16/skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.15-to-8.0.0-rc.16/) for upgrading extensions.
A date or time default is stored in its type's canonical form. `prisma contract emit` now refuses a default that the column's type does not hold.
-The Mongo ORM checks every value through its field's codec. A write of a value of the wrong type now fails with `RUNTIME.ENCODE_FAILED`.
-`temporal-polyfill` is a peer dependency of the Postgres packages. Projects using Yarn must add `temporal-polyfill` to their dependencies.
-The toolchain requires `@prisma/cli-engine` 0.6.2. Projects pinning `@prisma/cli-engine` must update to 0.6.2.
+Serverless connection now has `db.orm`, `db.transaction(...)`, and `db.prepare(...)`, making it compatible with code written for `postgres()` clients.
+Postgres CLI commands now work with date and time defaults on Node 24.
migration_steps3 steps
01Update `@prisma/cli-engine` to 0.6.2 if pinned.
02Add `temporal-polyfill` to dependencies if using Yarn.
03Follow the app and extension recipes for detailed migration steps.
PSL models without `@@map` now name their tables exactly as written, requiring explicit `@@map` for previous behavior.
-Every PSL schema file must start with `// use prisma-8` to be included in the contract.
-`dbgenerated(...)` is removed; raw SQL defaults must use `sql` tagged literals.
-Column defaults must now be values that the column's data type accepts.
!`.defaultSql('...')` in TypeScript contract builder is deprecated in favor of `.default(now())`, `.default(autoincrement())`, or ``.default(sql`...`)``.
+Postgres full-text search support.
+Prepared ORM reads and aggregates.
+Schemas can now be split across several files.
+Prisma 7 projects can use their existing `schema.prisma` as the Prisma 8 contract source.
migration_steps5 steps
01Update `@prisma/cli-engine` to version 0.6.1 and replace `defineConfig` with `definePrismaConfig`.
02Run the `add-model-map` script to add `@@map` to models without it.
03Add `// use prisma-8` to the first line of every PSL schema file.
04Replace `dbgenerated(...)` with `sql` tagged literals or appropriate functions like `now()`.
05Ensure column defaults match the column's data type.
01Follow the [app recipe](https://github.com/prisma/orm/blob/v8.0.0-rc.11/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.10-to-8.0.0-rc.11/) for upgrading applications.
02Follow the [extension recipe](https://github.com/prisma/orm/blob/v8.0.0-rc.11/skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.10-to-8.0.0-rc.11/) for upgrading extensions.
To-one relations record their nullability in the contract. Run `prisma contract emit` once after upgrading to update `contract.d.ts` with the new `Models` namespace.
!The schema header `// use prisma-next` is deprecated in favor of `// use prisma-8`. The old header still works but will be rewritten to the new form when formatting the file.
+Named model and result types in `contract.d.ts` with `Models` namespace and `models` constant.
+Attribute completion in the language server for field, model, and block attributes.
+`db sign` can choose or skip the ref it advances with `--advance-ref` and `--no-advance-ref` options.
migration_steps2 steps
01Rename `PRISMA_NEXT_*` environment variables to `PRISMA_*`.
02Run `prisma contract emit` to update `contract.d.ts` with the new `Models` namespace.
The `prisma-8` skill now teaches agents the migration system's real model, preventing full-create plans against real databases.
migration_steps1 steps
01Follow the [user recipe](https://github.com/prisma/prisma/tree/v8.0.0-rc.8/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.7-to-8.0.0-rc.8/) for upgrading from v8.0.0-rc.7 to v8.0.0-rc.8.
`prisma orm init` no longer installs agent skills; this functionality is moved to the family-level `prisma init` command.
-The engine peer dependency has been updated to `@prisma/cli-engine@0.2.2`, which includes fixes for pnpm symlink layouts and CI detection.
+The prisma-8 skill is now included in npm tarballs (`@prisma/orm-postgres`, `@prisma/orm-sqlite`, `@prisma/orm-mongo`), allowing `prisma skills sync` to detect staleness from installed packages.
migration_steps3 steps
01Choose a representation (`Temporal` or text) for each PostgreSQL temporal column and re-emit contracts.
02Update to `@prisma/cli-engine@0.2.2` if manually pinned.
03Use `prisma init` instead of `prisma orm init` for agent skills setup.