v6.16.3

Today, we are issuing a 6.16.3 patch release focused on bug fixes.

🛠 Fixes

• Prisma Client (prisma-client generator): fixed missing JSON null type definitions (JsonNull, DbNull, AnyNull) in the browser.ts entrypoint. (https://github.com/prisma/prisma/pull/28186)

• Prisma Migrate: don't add the default schema (namespace) to the generated migrations unless it was specified explicitly in the schema file. This restores the pre-6.13.0 behaviour that was inadvertently changed with enabling multi-schema support by default. Users who rely on database schemas for multi-tenancy can now again use the same migration files for all of their schemas. (https://github.com/prisma/prisma-engines/pull/5614)

• Prisma Client: enabled negative take with findFirst again. (https://github.com/prisma/prisma-engines/pull/5616 — contributed by @jay-l-e-e)

• Prisma Accelerate: aligned the behaviour of the new Rust-free client with Query Engine to handle self-signed certificates consistently and ensure backward compatibility. (https://github.com/prisma/prisma/pull/28134)

• @prisma/adapter-mariadb: fixed error event listeners leak. (https://github.com/prisma/prisma/pull/28177 — contributed by @Tiaansu)

⚠️ Known Limitation: JSON null types in browser builds

The fix introduces the missing types, but the singleton instances differ between the client and browser entrypoints of the generated client. This means that values like Prisma.JsonNull imported from browser cannot yet be assigned to fields expected from the client entrypoint, and vice versa. This results in confusing TypeScript errors if you mix them. A follow-up improvement is planned to unify these utility types across entrypoints.