unstale

npm / @prisma/adapter-pg

@prisma/adapter-pg

What changed in @prisma/adapter-pg 6 to 7, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-27.

5 breaking1 behavior and defaults

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.8 on npm

@prisma/adapter-pg 74 changes

Breaking changes 3

  • The adapter uses the underlying Node.js driver’s pool settings, which can differ from Prisma ORM v6 defaults; for example, pg has no connection timeout by default.

    7.0.0upgrade guide

  • Creating a Prisma Client now requires a driver adapter; PostgreSQL users pass a PrismaPg instance to PrismaClient.

    7.0.0upgrade guide

  • Invalid SSL certificates are no longer ignored by default; configure certificates or set ssl.rejectUnauthorized to false to keep the previous behavior.

    7.0.0upgrade guide

Behavior and default changes 1

  • PrismaPg requires a direct database connection string and fails when passed a Prisma Accelerate URL.

    7.0.0upgrade guide

@prisma/adapter-pg 62 changes

Breaking changes 2

  • Prisma ORM v6 requires Node.js 18.18.0, 20.9.0, or 22.11.0 at minimum; Node.js 16, 17, 19, and 21 are not officially supported.

    6.0.0upgrade guide

  • Prisma ORM v6 raises the minimum supported TypeScript version to 5.1.0.

    6.0.0upgrade guide