Packages

@prisma/config

7.10.1 · 15 Oct 2026Apache-2.021.6M / weekRepositorynpmAtom feed

Upgrading @prisma/config From 6.16.2 to 6.19.3

8 releases in betweenevery note read

Other targets from 6.16.2Latest7.10.1
  1. 6.16.2yours
  2. 6.16.3
  3. 6.17.0
  4. 6.17.1
  5. 6.18.0
  6. 6.19.0
  7. 6.19.1
  8. 6.19.2
  9. 6.19.3target
0
changes to make
0
advisories fixed
11
new
6
fixes

Security

  • It updates the effect dependency to resolve a security vulnerability.

    6.19.3

Release by release

  1. 6.19.3

    Security fix1 Apr 2026
    • security

      It updates the effect dependency to resolve a security vulnerability.

  2. 6.19.1 – 6.19.22 releases, nothing new or fixed in the notes

  3. 6.19.0

    5 Nov 20256 new
    • new

      When dropping a model from a schema, do not append the default schema to the migration.

    • new

      Align naming conventions for fields and relation fields

    • new

      Add biome ignore comments to generated client files. This was a community contribution from @lonelyevil, thank you!

    • new

      Unified Prisma Config for project configuration

    • new

      Move from prisma-client-js prisma-client

    • new

      New engine and datasource keys in prisma.config.ts

  4. 6.18.0

    22 Oct 20251 new
    • new

      Support for defining your datasource in prisma.config.ts

  5. 6.17.1nothing new or fixed in the note

  6. 6.17.0

    7 Oct 20254 new · 1 fix
    • new

      Added support for Entra ID (ActiveDirectory) authentication parameters for the MS SQL Server driver adapter. For example, you can use the config object to configure DefaultAzureCredential:

    • new

      Relaxed the support package range for @opentelemetry/instrumentation to be compatible with ">=0.52.0 <1". Learn more in this PR.

    • new

      Added Codex CLI detection, ensuring dangerous Prisma operations are not executed by Codex without explicit user consent. Learn more in this PR.

    • new

      Restored the original behaviour of group-by aggregations where they would refer to columns with explicit table names which fixes a regression that would result in ambiguous column errors. Learn more in this PR.

    • fixed

      Fixed JSON column handling when using a MariaDB database. Learn more in this PR.

  7. 6.16.3

    30 Sep 20255 fixes
    • fixed

      Prisma Client (prisma-client generator): fixed missing JSON null type definitions (JsonNull, DbNull, AnyNull) in the browser.ts entrypoint. (#28186)

    • fixed

      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. (#5614)

    • fixed

      Prisma Client: enabled negative take with findFirst again. _(#5616 — contributed

    • fixed

      Prisma Accelerate: aligned the behaviour of the new Rust-free client with Query Engine to handle self-signed certificates consistently and ensure backward compatibility. (#28134)

    • fixed

      @prisma/adapter-mariadb: fixed error event listeners leak. _(#28177 — contributed

13 other lines we could not sort, mostly version bumps

  • prisma init now creates a prisma.config.ts automatically

    6.18.0

  • #28291 Support multiple Prisma instances with different providers

    6.18.0

  • #28305 Add env helper function

    6.18.0

  • #28266 Add support for js or classic as engine types in prisma.config

    6.18.0

  • #28139 Map Bytes to Uint8Array depending on Typescript version

    6.18.0

  • Total egress

    6.18.0

  • Average response size

    6.18.0

  • Average query duration

    6.18.0

  • Estimated upcoming invoice

    6.17.0

  • Total storage used

    6.17.0

3 internal lines (docs, tests, tooling) left out.