chore(deps): bump @prisma/client from 4.16.2 to 5.3.1

[dependabot[bot]]

Bumps @prisma/client from 4.16.2 to 5.3.1.

Release notes

Sourced from @​prisma/client's releases.

5.3.1

Today, we are issuing the 5.3.1 patch release.

Fix in Prisma Client

• Duplicated keys in metrics properties

5.3.0

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

Highlights

In this sprint, we’ve made bug fixes and overall improvements to Prisma Client. We’ve been working on a few projects that will be announced soon. Stay tuned for the upcoming releases for updates!

Improvements and bug fixes

We made the following changes:

Prisma Client improvements

• Validation for undefined values in arrays in Json fields We added runtime validation for undefined values in arrays in Json fields. Prisma Client will now return an error when an array contains an undefined value. Therefore, we encourage you to add validation that either removes the value or transforms it to null if you stumble on the runtime validation:

// Query
await prisma.user.findMany({
 where: {
   // JSON field
   preferences: [undefined, '"theme": "dark"', null, ]
 }
})
// Example error message on running the query
Can not use undefined value within array. Use null or filter out undefined values

• Performance improvements for models with many unique fields

This release improves Prisma Client’s memory consumption for models with many @unique constraints. This was a regression from version 4.10.1, where in some cases, if a model had many unique constraints, Prisma Client would use up a lot of available memory.

• Fixed the segmentation fault error that used to occur on ARM64 Linux binary targets
• Metrics Preview feature improvements:
  • We updated the counters and gauge properties
  • We fixed the bug that caused the prisma_pool_connections_open metric to have a negative value in some cases.

Prisma Migrate improvements

• Fixed an introspection bug for MongoDB views. Previously, if a MongoDB database contained a view, prisma db pull would throw an error. We resolved this, and views are now ignored.
• Added the PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK environment variable that enables you to disable advisory locking.

... (truncated)

Commits

• 8e03651 chore(deps): patch 5.3.x 5.3.1-2.61e140623197a131c2a6189271ffee05a7aa9a59 (#2...
• dc54aed chore(deps): update engines to 5.3.0-36.e90b936d84779543cbe0e494bc8b9d7337fad...
• 0b8edfb chore(deps): update engines to 5.3.0-35.ae074a73c82cffe83fa074ac12510c28a868b...
• 0b1b958 chore(deps): update engines to 5.3.0-34.9b21b9f1a34ef29c3992abdb81d40c3817475...
• 92cde26 chore: remove data proxy special handling in tests (#20935)
• b2bc015 chore(deps): update engines to 5.3.0-31.1816b81529d375ba16b9173156a20b3e0b51a...
• 87bdf31 chore(deps): update engines to 5.3.0-29.319461411f708bb91a5dd85ee797de71db841...
• 1961e3e chore(deps): update dependency tsd to v0.29.0 (#20978)
• ff5749d chore(deps): update dependency @​fast-check/jest to v1.7.2 (#20975)
• b1e5de0 chore(deps): update engines to 5.3.0-28.3457e5de04da1741c969a80068702ad103e99...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.