[Snyk] Upgrade @prisma/client from 5.5.2 to 5.6.0

[max-de-bug]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade @prisma/client from 5.5.2 to 5.6.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 162 versions ahead of your current version.
• The recommended version was released 21 days ago, on 2023-11-14.

Release notes

Package name: @prisma/client

• 5.6.0 - 2023-11-14
  

  🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

  🚀 Prisma Accelerate, our connection pool and global edge cache, is now Generally Available! Sign up to give it a try. 🚀

  Highlights

  Driver adapters improvements (Preview)

  In version 5.4.0, we released driverAdapters into Preview. The driverAdapters feature enables Prisma Client to access your database using JavaScript or Serverless database drivers.

  In this release, we fixed many bugs for the existing driver adapters. We appreciate all the community feedback that has helped us improve this feature!

  PlanetScale serverless driver adapter improvements

  This release also introduces a small breaking change to the @ prisma/adapter-planetscale package to improve its stability and performance. The serverless driver adapter will now use a connection pool instead of a single connection from PlanetScale’s serverless driver.

  In case you’re using the @ prisma/adapter-planetscale, update your Prisma Client instance with the following:

  -import { connect } from '@ planetscale/database'
  +import { Client } from '@ planetscale/database'
  import { PrismaPlanetScale } from '@ prisma/adapter-planetscale'
  import { PrismaClient } from '@ prisma/client'
  import { fetch as undiciFetch } from 'undici';

  -const connection = connect({ url: connectionString, fetch: undiciFetch })
  +const client = new Client({ url: connectionString, fetch: undiciFetch })

  -const adapter = new PrismaPlanetScale(connection)
  +const adapter = new PrismaPlanetScale(client)

  const prisma = new PrismaClient({ adapter })

  If you run into the following error: [TypeError]: PrismaPlanetScale must be initialized with an instance of Client., you can use the following snippet when defining your Prisma Client instance:

  import { createRequire } from "node:module";
  import { PrismaPlanetScale } from "@ prisma/adapter-planetscale";
  import { fetch as undiciFetch } from 'undici';

  const require = createRequire(import.meta.url);
  const { Client } = require("@ planetscale/database");

  const client = new Client({ url: process.env.DATABASE_URL , fetch: undiciFetch })
  const adapter = new PrismaPlanetScale(client);

  Request for feedback

  We encourage you to try out the driver adapters and share your feedback to help us move it to General Availability in either of the following GitHub discussions:

  • Neon
  • PlanetScale
  • Turso

  Refer to our docs to learn more about driver adapters.

  New prisma debug command

  This release introduces a new command: prisma debug. The command provides debugging information such as environment variables that Prisma Client, Prisma Migrate, Prisma CLI, and Prisma Studio use. The command is also useful when creating a bug report as the information complements the output of the prisma -v command.

  You can learn more about the command in our docs.

  Read replicas extension improvements

  We also released version 0.3.0 of the @ prisma/extension-read-replicas package that contains the following improvements:

  • A new $replica() method that explicitly enables you to use a replica for your query.

    For example, by default, the queryRaw and executeRaw methods are forwarded to the primary database, as they could try to write to the database. You can use the $replica() method with either of the *Raw methods to explicitly execute your query against a replica instead of your primary database.

  • Validation for when there’s an empty list of replicas.

  • Webpack bundling fixes

  We want to thank you, our community members, for your contributions! 🙏

  You can find additional information on the changes in the extension’s release. You can learn more about the extension in the announcement blog post.

  Package provenance

  npm has introduced provenance statements to improve supply-chain security and transparency of packages. This allows developers to verify where and how packages are built.

  Starting with the 5.6.0 release, all npm packages for Prisma ORM will be published with provenance statements. If you maintain a Prisma Client extension or generator, we encourage you to enable provenance statements when publishing to npm.

  Fixes and improvements

  Prisma Migrate

  • Weird error message on db push with invalid connection string: Connection string redacted, weird grammar
  • Regression for MongoDB introspection in 5.4.0
  • Inconsistent datetime column data importing to Turso
  • db pull --url=... logs full connection string on P4001 The introspected database was empty

  Prisma Client

  • prisma_pool_connections_idle reports misleading number
  • Update and read issues with @prisma/adapter-planetscale
  • 5.5.0 regression: typescript error when trying to pass PrismaPlanetScale adapter to the constructor
  • 5.5.0/1: Error: sha256 checksum of https://binaries.prisma.sh/all_commits/475c616176945d72f4330c92801f0c5e6398dc0f/windows/query_en gine.dll.node.gz (zipped) should be 748d039badd0919d022fff7d554b66b6937b79035861a6ae9a80c5a95eee76f5 but is b867ad335ee6f58c6a38f665dd641c95e6adff3061f92b7613c62cae1c3362bb

  Prisma CLI

  • prisma debug

  Credits

  Huge thanks to @ onichandame, @ LucianBuzzo, @ RobertCraigie, @ fqazi, @ KhooHaoYit, @ alencardc, @ Oreilles, @ christianledgard, @ skyzh, @ alula, @ luxaritas, @ Nasfame, @ lukahartwig, @ steebchen, @ icanipa for helping!

  Company news

  Prisma Accelerate is now Generally Available

  We're excited to share that Prisma Accelerate is now Generally Available. Prisma Accelerate is a global database cache that's available in over 280 locations and provides scalable connection pooling for serverless and edge applications.

  Learn more in the announcement blog post. Sign up and try out Prisma Accelerate here.

  💼 We’re hiring!

  If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.

  We're hiring for an Engineering Manager: Prisma Data Platform.

• 5.6.0-integration-refactor-consistently-use-binarytarget-term.2 - 2023-10-31
• 5.6.0-integration-refactor-consistently-use-binarytarget-term.1 - 2023-10-30
• 5.6.0-integration-joel-node-fetch-publish.1 - 2023-10-31
• 5.6.0-integration-fix-planetscale-client.4 - 2023-11-10
• 5.6.0-integration-fix-planetscale-client.3 - 2023-11-10
• 5.6.0-integration-fix-planetscale-client.1 - 2023-11-10
• 5.6.0-integration-feat-client-wasm-engine.9 - 2023-11-01
• 5.6.0-integration-feat-client-wasm-engine.8 - 2023-11-01
• 5.6.0-integration-feat-client-wasm-engine.7 - 2023-11-01
• 5.6.0-integration-feat-client-wasm-engine.6 - 2023-10-31
• 5.6.0-integration-feat-client-wasm-engine.5 - 2023-10-31
• 5.6.0-integration-feat-client-wasm-engine.4 - 2023-10-31
• 5.6.0-integration-feat-client-wasm-engine.3 - 2023-10-31
• 5.6.0-integration-feat-client-wasm-engine.2 - 2023-10-26
• 5.6.0-integration-feat-client-wasm-engine.1 - 2023-10-24
• 5.6.0-integration-feat-auto-edge-import.3 - 2023-11-01
• 5.6.0-integration-feat-auto-edge-import.2 - 2023-11-01
• 5.6.0-integration-feat-auto-edge-import.1 - 2023-10-27
• 5.6.0-integration-engines-5-6-0-7-integration-bump-mobc-7278ed291ba8a8b6be9da5f7959a59084a3e19ae.2 - 2023-10-28
• 5.6.0-integration-engines-5-6-0-7-integration-bump-mobc-7278ed291ba8a8b6be9da5f7959a59084a3e19ae.1 - 2023-10-28
• 5.6.0-integration-engines-5-6-0-6-integration-engineer-dont-overwrite-engine-versions-01aa2621a92b5b3df1c7904ecda5970ec061c579.2 - 2023-10-27
• 5.6.0-integration-engines-5-6-0-6-integration-engineer-dont-overwrite-engine-versions-01aa2621a92b5b3df1c7904ecda5970ec061c579.1 - 2023-10-27
• 5.6.0-integration-engines-5-6-0-31-integration-bump-mobc-d19bcc65cdabf1db98633bb5aa496b2bf2f6046d.2 - 2023-11-13
• 5.6.0-integration-engines-5-6-0-31-integration-bump-mobc-d19bcc65cdabf1db98633bb5aa496b2bf2f6046d.1 - 2023-11-13
• 5.6.0-integration-engines-5-6-0-26-integration-bump-mobc-14aff2880480b5db1569ca98339eb75f33a2b6bb.2 - 2023-11-13
• 5.6.0-integration-engines-5-6-0-26-integration-bump-mobc-14aff2880480b5db1569ca98339eb75f33a2b6bb.1 - 2023-11-13
• 5.6.0-integration-engines-5-6-0-22-integration-sql-nested-transactions-4c2470361c7aef1441e5cf3c5b517f19ab30c87a.2 - 2023-11-08
• 5.6.0-integration-engines-5-6-0-22-integration-sql-nested-transactions-4c2470361c7aef1441e5cf3c5b517f19ab30c87a.1 - 2023-11-08
• 5.6.0-integration-engines-5-6-0-20-integration-ps-datetime-fidelity-e596b1a3d11a649b11e48da239c60e780cbaf9e2.2 - 2023-11-08
• 5.6.0-integration-engines-5-6-0-20-integration-ps-datetime-fidelity-e596b1a3d11a649b11e48da239c60e780cbaf9e2.1 - 2023-11-08
• 5.6.0-integration-engines-5-6-0-18-integration-mff-517-e06ca3d983a0c00cb2158d6b2f530562d119751b.4 - 2023-11-07
• 5.6.0-integration-engines-5-6-0-18-integration-mff-517-e06ca3d983a0c00cb2158d6b2f530562d119751b.3 - 2023-11-07
• 5.6.0-integration-engines-5-6-0-18-integration-mff-517-e06ca3d983a0c00cb2158d6b2f530562d119751b.2 - 2023-11-07
• 5.6.0-integration-engines-5-6-0-18-integration-mff-517-e06ca3d983a0c00cb2158d6b2f530562d119751b.1 - 2023-11-07
• 5.6.0-integration-engines-5-6-0-17-integration-mff-517-18ad27daee2d562b8d75e34b5b30da2fc6a6ef17.2 - 2023-11-07
• 5.6.0-integration-engines-5-6-0-17-integration-mff-517-18ad27daee2d562b8d75e34b5b30da2fc6a6ef17.1 - 2023-11-07
• 5.6.0-integration-engines-5-6-0-16-integration-mff-517-687b72e4b3791deb25ec1af8b20ace67cf68bc85.2 - 2023-11-07
• 5.6.0-integration-engines-5-6-0-16-integration-mff-517-687b72e4b3791deb25ec1af8b20ace67cf68bc85.1 - 2023-11-07
• 5.6.0-integration-engines-5-6-0-14-integration-sql-nested-transactions-5a0f60fe78f2029f692e21ce8732a978466b9baf.2 - 2023-11-01
• 5.6.0-integration-engines-5-6-0-14-integration-sql-nested-transactions-5a0f60fe78f2029f692e21ce8732a978466b9baf.1 - 2023-11-01
• 5.6.0-integration-engines-5-6-0-13-janpio-sql-nested-transactions-07d231288d1a9b62fb7af3764745b75447d5d2b7.1 - 2023-11-01
• 5.6.0-integration-engines-5-6-0-12-integration-sql-nested-transactions-a8af640da343c10e0f7421264c2838b302d3ce6d.2 - 2023-11-01
• 5.6.0-integration-engines-5-6-0-12-integration-sql-nested-transactions-a8af640da343c10e0f7421264c2838b302d3ce6d.1 - 2023-11-01
• 5.6.0-integration-engines-5-6-0-10-integration-bump-mobc-e4056297dc83a2ee095f9f9fb637fc1dbc167b73.2 - 2023-10-30
• 5.6.0-integration-engines-5-6-0-10-integration-bump-mobc-e4056297dc83a2ee095f9f9fb637fc1dbc167b73.1 - 2023-10-30
• 5.6.0-integration-debug-nodemodule-hack.2 - 2023-11-02
• 5.6.0-integration-debug-nodemodule-hack.1 - 2023-11-02
• 5.6.0-integration-chore-upgrade-esm-deps.16 - 2023-10-31
• 5.6.0-integration-chore-upgrade-esm-deps.15 - 2023-10-31
• 5.6.0-integration-chore-upgrade-esm-deps.14 - 2023-10-31
• 5.6.0-integration-chore-upgrade-esm-deps.13 - 2023-10-30
• 5.6.0-integration-chore-upgrade-esm-deps.12 - 2023-10-30
• 5.6.0-integration-chore-upgrade-esm-deps.11 - 2023-10-30
• 5.6.0-integration-chore-upgrade-esm-deps.10 - 2023-10-30
• 5.6.0-integration-chore-upgrade-esm-deps.9 - 2023-10-28
• 5.6.0-integration-chore-upgrade-esm-deps.8 - 2023-10-28
• 5.6.0-integration-chore-upgrade-esm-deps.7 - 2023-10-27
• 5.6.0-integration-chore-upgrade-esm-deps.6 - 2023-10-27
• 5.6.0-integration-chore-upgrade-esm-deps.5 - 2023-10-27
• 5.6.0-integration-chore-upgrade-esm-deps.4 - 2023-10-27
• 5.6.0-integration-chore-upgrade-esm-deps.3 - 2023-10-27
• 5.6.0-integration-chore-upgrade-esm-deps.2 - 2023-10-27
• 5.6.0-integration-chore-upgrade-esm-deps.1 - 2023-10-27
• 5.6.0-integration-chore-client-adapter-porting-nits.6 - 2023-10-30
• 5.6.0-integration-chore-client-adapter-porting-nits.5 - 2023-10-30
• 5.6.0-integration-chore-client-adapter-porting-nits.3 - 2023-10-27
• 5.6.0-integration-chore-client-adapter-porting-nits.2 - 2023-10-27
• 5.6.0-integration-chore-client-adapter-porting-nits.1 - 2023-10-27
• 5.6.0-dev.104 - 2023-11-14
• 5.6.0-dev.103 - 2023-11-14
• 5.6.0-dev.102 - 2023-11-14
• 5.6.0-dev.101 - 2023-11-14
• 5.6.0-dev.100 - 2023-11-13
• 5.6.0-dev.99 - 2023-11-13
• 5.6.0-dev.98 - 2023-11-13
• 5.6.0-dev.97 - 2023-11-13
• 5.6.0-dev.96 - 2023-11-13
• 5.6.0-dev.95 - 2023-11-13
• 5.6.0-dev.94 - 2023-11-13
• 5.6.0-dev.93 - 2023-11-13
• 5.6.0-dev.92 - 2023-11-13
• 5.6.0-dev.91 - 2023-11-13
• 5.6.0-dev.90 - 2023-11-13
• 5.6.0-dev.89 - 2023-11-13
• 5.6.0-dev.88 - 2023-11-10
• 5.6.0-dev.87 - 2023-11-10
• 5.6.0-dev.86 - 2023-11-10
• 5.6.0-dev.85 - 2023-11-10
• 5.6.0-dev.84 - 2023-11-09
• 5.6.0-dev.83 - 2023-11-09
• 5.6.0-dev.82 - 2023-11-09
• 5.6.0-dev.81 - 2023-11-08
• 5.6.0-dev.80 - 2023-11-08
• 5.6.0-dev.79 - 2023-11-08
• 5.6.0-dev.75 - 2023-11-07
• 5.6.0-dev.74 - 2023-11-07
• 5.6.0-dev.73 - 2023-11-07
• 5.6.0-dev.72 - 2023-11-06
• 5.6.0-dev.71 - 2023-11-06
• 5.6.0-dev.70 - 2023-11-06
• 5.6.0-dev.69 - 2023-11-06
• 5.6.0-dev.68 - 2023-11-06
• 5.6.0-dev.67 - 2023-11-06
• 5.6.0-dev.66 - 2023-11-06
• 5.6.0-dev.65 - 2023-11-06
• 5.6.0-dev.64 - 2023-11-06
• 5.6.0-dev.63 - 2023-11-06
• 5.6.0-dev.62 - 2023-11-06
• 5.6.0-dev.61 - 2023-11-06
• 5.6.0-dev.60 - 2023-11-06
• 5.6.0-dev.59 - 2023-11-05
• 5.6.0-dev.58 - 2023-11-03
• 5.6.0-dev.57 - 2023-11-03
• 5.6.0-dev.56 - 2023-11-01
• 5.6.0-dev.55 - 2023-11-01
• 5.6.0-dev.54 - 2023-11-01
• 5.6.0-dev.53 - 2023-11-01
• 5.6.0-dev.52 - 2023-11-01
• 5.6.0-dev.51 - 2023-11-01
• 5.6.0-dev.49 - 2023-11-01
• 5.6.0-dev.48 - 2023-11-01
• 5.6.0-dev.47 - 2023-11-01
• 5.6.0-dev.46 - 2023-11-01
• 5.6.0-dev.45 - 2023-10-31
• 5.6.0-dev.44 - 2023-10-31
• 5.6.0-dev.43 - 2023-10-31
• 5.6.0-dev.42 - 2023-10-31
• 5.6.0-dev.41 - 2023-10-31
• 5.6.0-dev.40 - 2023-10-31
• 5.6.0-dev.39 - 2023-10-30
• 5.6.0-dev.38 - 2023-10-30
• 5.6.0-dev.36 - 2023-10-30
• 5.6.0-dev.35 - 2023-10-30
• 5.6.0-dev.34 - 2023-10-30
• 5.6.0-dev.33 - 2023-10-30
• 5.6.0-dev.32 - 2023-10-30
• 5.6.0-dev.26 - 2023-10-30
• 5.6.0-dev.25 - 2023-10-30
• 5.6.0-dev.24 - 2023-10-27
• 5.6.0-dev.23 - 2023-10-27
• 5.6.0-dev.22 - 2023-10-27
• 5.6.0-dev.21 - 2023-10-27
• 5.6.0-dev.20 - 2023-10-27
• 5.6.0-dev.19 - 2023-10-26
• 5.6.0-dev.18 - 2023-10-26
• 5.6.0-dev.17 - 2023-10-26
• 5.6.0-dev.16 - 2023-10-26
• 5.6.0-dev.15 - 2023-10-26
• 5.6.0-dev.14 - 2023-10-25
• 5.6.0-dev.13 - 2023-10-25
• 5.6.0-dev.12 - 2023-10-25
• 5.6.0-dev.11 - 2023-10-25
• 5.6.0-dev.10 - 2023-10-25
• 5.6.0-dev.9 - 2023-10-24
• 5.6.0-dev.8 - 2023-10-24
• 5.6.0-dev.7 - 2023-10-24
• 5.6.0-dev.5 - 2023-10-24
• 5.6.0-dev.4 - 2023-10-24
• 5.6.0-dev.3 - 2023-10-24
• 5.6.0-dev.2 - 2023-10-24
• 5.6.0-dev.1 - 2023-10-24
• 5.5.2 - 2023-10-25
  

  Today, we are issuing the 5.5.2 patch release.

  Fix in Prisma CLI

  • Error: sha256 checksum of https://binaries.prisma.sh/all_commits/475c616176945d72f4330c92801f0c5e6398dc0f/windows/query_en gine.dll.node.gz (zipped) should be 748d039badd0919d022fff7d554b66b6937b79035861a6ae9a80c5a95eee76f5 but is b867ad335ee6f58c6a38f665dd641c95e6adff3061f92b7613c62cae1c3362bb

from @prisma/client GitHub release notes

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs