Prisma 6.13.0 — Release Notes & Engineering Impact

Today, we are excited to share the `6.13.0` stable release 🎉 **🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!** ## Highlights In this ORM release, we’re moving the Prisma Config file and the multi-schema feature into [General Availability](https://www.prisma.io/docs/orm/more/releases#generally-available-ga). This means these features now are fully production-ready and we’re looking forward to seeing what you are going to build with them! Additionally, support for SQL views is getting an important update to further stabilize its API. ### Configuring Prisma via Prisma Config is now Generally Available The [`prisma.config.ts`](https://www.prisma.io/docs/orm/reference/prisma-config-reference) file is Prisma ORM’s native way to provide configuration options for your project. It currently lets you specify: - the locations for various Prisma-related assets, such as your: - Prisma schema file - migrations - SQL view definitions - TypedSQL queries - a `seed` command to populate your database based on some executable script - externally managed tables (see below) - the driver adapters to be used by the Prisma CLI when interacting with your database Here’s an example Prisma Config file that specified custom locations for various project assets in and a seed script inside a `db` directory: ```tsx import path from "node:path"; import { defineConfig } from "prisma/config"; export default defineConfig({ schema: path.join("db", "schema.prisma"), migrations: { path: path.join("db", "migrations"), seed: "tsx db/seed.ts" } }); ``` Note that you’ll also see warning now if you defined a `prisma.seed` command in `package.json`. We’re excited to move the [`prisma.config.ts`](https://www.prisma.io/docs/orm/reference/prisma-config-reference) file into General Availability. If you used it before in your projects, you can now drop `earlyAccess` from its options: ```diff import { defineConfig } from "prisma/config"; export default defineConfig({ - earlyAccess: true, }); ``` There still are and will be fields on the Prisma Config object that are Early Access or Preview features. To opt-into these, you’ll need to explicitly declare them via a new `experimental` field. For example, usage of `adapters` is currently still in Preview: ```tsx import { defineConfig } from "prisma/config"; export default defineConfig({ experimental: { adapter: true, }, // requires `experimental.adapter` adapter: async () => { // ... }, }); ``` Finally, the Prisma Config file now also supports various file extensions so it fits neatly into your individual project setups: `.js`, `.ts`, `.mjs`, `.cjs`, `.mts`, `.cts`. It also can be defined as `.config/prisma.${extension}`, where `extension` is the same one as file extensions above. 📚 Learn more [in the docs](https://www.prisma.io/docs/orm/reference/prisma-config-reference). ### Using multiple schemas in now Generally Available Databases like PostgreSQL or SQL Server provide a way to logically organize your tables in dedicated namespaces called *schemas*. In Prisma ORM, you can assign tables to various schemas via the `@@schema` attribute: ```tsx datasource db { provider = "postgresql" url = env("DATABASE_URL") schemas = ["base", "shop"] } model User { id Int @id orders Order[] @@schema("base") } model Order { id Int @id user User @relation(fields: [userId], references: [id]) userId Int @@schema("shop") } ``` This feature has moved into General Availability, so if you were using it before, you can now drop the `multiSchema` feature flag from the `generator` block in your Prisma schema: ```diff generator client { // ... - previewFeatures = ["multiSchema"] } ``` 📚 Learn more [in the docs](https://www.prisma.io/docs/orm/prisma-schema/data-model/multi-schema). ### More robust support for SQL views (Preview) SQL views are *virtual* tables created by a query. Unlike regular tables, views do not store data themselves; instead, they represent the result of a stored SQL query that runs whenever the view is accessed. We continue to improve support for SQL views, making them more reliable and better aligned with Prisma’s features. In this release, we ensured that `@id`, `@index` and `@unique` can’t be used on a `view` block in the Prisma schema. Without these attributes, several other features in Prisma Client or the Prisma schema don’t make sense any more either, so we made sure that they can’t be used with views: - disabled `findUnique` queries and cursor-based pagination in Prisma Client - disallowed writes and implicit ordering for views in Prisma Client - disallowed relationships involving views in Prisma Schema This will align the API surface of Prisma ORM with the actual capabilities of SQL views and adds guardrails so you can use views with more confidence! 📚 Learn more [in the docs](https://www.prisma.io/docs/orm/prisma-schema/data-model/views). ### Externally managed tables In some situations, you may not want Prisma ORM to be “responsible” for specific tables in your database because they’re being managed by a different team in your organization or an external service. In these cases, you still may want to quert these tables using Prisma Client but never want Prisma Migrate to make any changes to them. In this release, we’re introducing externally managed tables that will be: - ignored by Prisma Migrate - queryable via Prisma Client You can specify which tables should be ignored by Prisma Migrate using the `tables` option in `prisma.config.ts`: ```tsx // prisma.config.ts export default defineConfig({ tables: { external: [ "users", ] }, ... }) ``` A typical use case for this is the [`users` table from Supabase](https://supabase.com/docs/guides/auth/managing-user-data) which you never want be changed by Prisma Migrate but still may want to query with Prisma Client. 📚 Learn more [in the docs](https://www.prisma.io/docs/orm/prisma-schema/data-model/externally-managed-tables). ## Other news ### [`pgvector`](https://github.com/pgvector/pgvector) extension support for Prisma Postgres (Early Access) In this release, we’ve implemented a highly popular feature request for Prisma Postgres: [Early Access](https://www.prisma.io/docs/platform/maturity-levels#early-access) support for the [`pgvector`](https://github.com/pgvector/pgvector) PostgreSQL extension along with several other popular Postgres extensions! It enables efficient storage and querying of high-dimensional vector embeddings directly in a Postgres database and thus is perfect for building AI-driven applications. `pgvector` essentially allows developers to perform similarity search (e.g., for recommendation systems or semantic search) using standard SQL, eliminating the need for a separate vector database. Native support for `pgvector` in Prisma ORM is going to follow soon, until then you can use `pgvector` via [custom migrations](https://www.prisma.io/docs/orm/prisma-migrate/workflows/customizing-migrations) and [TypedSQL](https://www.prisma.io/blog/announcing-typedsql-make-your-raw-sql-queries-type-safe-with-prisma-orm). > **Note**: For now, `pgvector` is only available on *newly created* Prisma Postgres instances. It will be rolled out for *existing* instances soon. > In addition to `pgvector`, Prisma Postgres now includes Early Access support for `pg_search`, `pg_stat_statements`, `citext`, `pg_trgm`, `fuzzystrmatch`, and `unaccent`. If you don’t see the extension you need, you can [request it here](https://pris.ly/i-want-extensions). 📚 Learn more [in the docs](https://www.prisma.io/docs/postgres/database/postgres-extensions). ### Manage Prisma Postgres programmatically via an API Whether you need a way to quickly provision a Prisma Postgres instance in your CI/CD workflows, want to attach a fresh database to a preview branch of your app or even want to offer Prisma Postgres to your own users—our new Management API has you covered! It’s shaped as a familiar REST API so you can programmatically take care of your database workflows: Provision or delete Prisma Postgres instances, retrieve or create connection strings and manage entire projects in [Prisma Console](https://console.prisma.io/). 📚 Learn more [in the docs](https://www.prisma.io/docs/postgres/database/api-reference/management-api). ### CI/CD GitHub Actions for Prisma Postgres available on GitHub Marketplace Based on the Management API, we’ve also published two templates for GitHub Actions that you can use in your own CI/CD setups: - [**Create Prisma Postgres Database Action**](https://github.com/marketplace/actions/create-prisma-postgres-database) - [**Delete Prisma Postgres Database Action**](https://github.com/marketplace/actions/delete-prisma-postgres-database) These Actions serve as the foundational building blocks for integrating Prisma Postgres into CI/CD pipelines.  They enable workflows like provisioning databases on every pull request, running integration tests against real instances, and managing database lifecycles end-to-end. We’ve included several examples in the README to help users get started quickly. The setup is straightforward, and these Actions are designed to plug into user's workflows with minimal effort. ### Instant Postgres with `npx create-db` — no auth required We launched a new CLI command that allows you to spin up a new database within seconds: ```bash npx create-db # no auth required ``` The command doesn’t require authentication, so you can play around with your database without any initial hurdles!  Your instance will be automatically deleted after 24 hours *but* you can claim it and put it into your [Prisma Console](https://console.prisma.io) account if you want to keep using it after that period. Visit [the docs](https://www.prisma.io/docs/postgres/introduction/npx-create-db) to learn more. ### New navigation UI for [Prisma Console](https://console.prisma.io/) The [Prisma Console](https://console.prisma.io) got a little makeover, including a new design for navigating and managing your projects and their databases. This makes common workflows like *creating new projects*, *navigating between projects and databases*, as well as *accessing project settings* a lot more smooth.  We’re eager to hear your feedback, [let us know on X](https://pris.ly/x) what you think of the new UI. ## Enterprise support Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance. With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: [https://prisma.io/enterprise](https://prisma.io/enterprise).