# Prisma 6.16.3 — Release & Upgrade Intelligence
- **Product:** Prisma (https://prisma.io)
- **Version:** 6.16.3
- **Released:** Sep 30, 2025
- **Impact Score:** 5/10
- **Breaking Changes:** Not verified
- **Canonical Analysis:** https://changelogs.us/prisma/updates/6.16.3/

## Executive Summary (TL;DR)
Prisma 6.16.3. Source highlight: Today, we are issuing a 6.16.3 patch release focused on bug fixes.

## Bug 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)_

## Upgrade Command
```bash
npm install --save-dev --save-exact prisma@6.16.3
```