[dependabot]

Bumps the prisma group with 3 updates in the / directory: @prisma/adapter-pg, @prisma/client and prisma.

Updates @prisma/adapter-pg from 7.10.0 to 7.10.1

Release notes

Sourced from @​prisma/adapter-pg's releases.

7.10.1

Prisma ORM 7.10.1 is a patch release. It fixes a bug where a nested interactive transaction could make later, unrelated transactions run inside the wrong transaction. It also updates dependencies that had security advisories.

Fixes

Prisma Client: nested $transaction no longer changes the options object you pass in

If you passed the same options object to a nested tx.$transaction(...) and later to a top-level prisma.$transaction(...), the nested call wrote the outer transaction's id into that object. Every later top-level transaction that used the object was then treated as nested inside that old transaction:

• if the old transaction had committed, the new one failed with P2028;
• if the old transaction was still open, the new one silently ran as a savepoint inside another request's transaction.

const TX_OPTIONS = { timeout: 30_000, maxWait: 10_000 }
await prisma.$transaction(async (tx) => {
await tx.$transaction(async (inner) => { /* ... */ }, TX_OPTIONS)
})
// Before 7.10.1, this call could fail with P2028 or join another transaction.
await prisma.$transaction(async (tx) => { /* ... */ }, TX_OPTIONS)

Prisma Client no longer modifies the options object. (prisma/orm#30368, thanks @​lazerg)

Prisma Migrate: refuse a shadow database that is the main database

Prisma Migrate now refuses to run with error P3025 when the shadow database URL points at the same database as the main database URL. Before, prisma migrate diff --from-migrations with that setup dropped the real schema, rebuilt it from the migrations, and reported an empty diff. (prisma/prisma-engines#5851)

MariaDB adapter: updated to mariadb 3.5.4

@prisma/adapter-mariadb now depends on mariadb 3.5.4, which fixes several security advisories in 3.5.3. The adapter no longer rewrites IPv6 hosts in connection strings, because mariadb 3.5.4 accepts them as written. IPv6 connection strings keep working without changes. (prisma/orm#30668)

Dependency updates

Dependencies with security advisories were updated: mysql2, fast-uri, deepmerge-ts, mariadb and source-map-js. (prisma/orm#30314, prisma/orm#30189, prisma/orm#30668)

Commits

• 97ea359 fix(client): stop nested $transaction from mutating the caller's options obje...
• d329959 fix(v7): repair CI on every v7 pull request, and update mariadb to 3.5.4 with...
• 9afb1a4 chore(deps): bump mysql2 and fast-uri past audited vulnerabilities (#30314)
• 3dcc5b3 chore(deps): update engines to 8.1.0-1.d1b3f377ca835d73fd50954a5e22128b9ebdd6...
• 93118fd chore(deps): bump deepmerge-ts and mariadb past audited vulnerabilities (#30189)
• 9cb9c08 test(e2e): run prisma init from the local tarball in the corepack test (#30183)
• 9028ed8 ci: update github.repository checks for the rename to prisma/orm (#30180)
• 312e543 chore: update npm provenance repository (#30146)
• See full diff in compare view

Updates @prisma/client from 7.10.0 to 7.10.1

Release notes

Sourced from @​prisma/client's releases.

7.10.1

Prisma ORM 7.10.1 is a patch release. It fixes a bug where a nested interactive transaction could make later, unrelated transactions run inside the wrong transaction. It also updates dependencies that had security advisories.

Fixes

Prisma Client: nested $transaction no longer changes the options object you pass in

If you passed the same options object to a nested tx.$transaction(...) and later to a top-level prisma.$transaction(...), the nested call wrote the outer transaction's id into that object. Every later top-level transaction that used the object was then treated as nested inside that old transaction:

• if the old transaction had committed, the new one failed with P2028;
• if the old transaction was still open, the new one silently ran as a savepoint inside another request's transaction.

const TX_OPTIONS = { timeout: 30_000, maxWait: 10_000 }
await prisma.$transaction(async (tx) => {
await tx.$transaction(async (inner) => { /* ... */ }, TX_OPTIONS)
})
// Before 7.10.1, this call could fail with P2028 or join another transaction.
await prisma.$transaction(async (tx) => { /* ... */ }, TX_OPTIONS)

Prisma Client no longer modifies the options object. (prisma/orm#30368, thanks @​lazerg)

Prisma Migrate: refuse a shadow database that is the main database

Prisma Migrate now refuses to run with error P3025 when the shadow database URL points at the same database as the main database URL. Before, prisma migrate diff --from-migrations with that setup dropped the real schema, rebuilt it from the migrations, and reported an empty diff. (prisma/prisma-engines#5851)

MariaDB adapter: updated to mariadb 3.5.4

@prisma/adapter-mariadb now depends on mariadb 3.5.4, which fixes several security advisories in 3.5.3. The adapter no longer rewrites IPv6 hosts in connection strings, because mariadb 3.5.4 accepts them as written. IPv6 connection strings keep working without changes. (prisma/orm#30668)

Dependency updates

Dependencies with security advisories were updated: mysql2, fast-uri, deepmerge-ts, mariadb and source-map-js. (prisma/orm#30314, prisma/orm#30189, prisma/orm#30668)

Commits

• 97ea359 fix(client): stop nested $transaction from mutating the caller's options obje...
• d329959 fix(v7): repair CI on every v7 pull request, and update mariadb to 3.5.4 with...
• 9afb1a4 chore(deps): bump mysql2 and fast-uri past audited vulnerabilities (#30314)
• 3dcc5b3 chore(deps): update engines to 8.1.0-1.d1b3f377ca835d73fd50954a5e22128b9ebdd6...
• 93118fd chore(deps): bump deepmerge-ts and mariadb past audited vulnerabilities (#30189)
• 9cb9c08 test(e2e): run prisma init from the local tarball in the corepack test (#30183)
• 9028ed8 ci: update github.repository checks for the rename to prisma/orm (#30180)
• 312e543 chore: update npm provenance repository (#30146)
• See full diff in compare view

Updates prisma from 7.10.0 to 7.10.1

Commits

• See full diff in compare view