⬆️ Bump @prisma/client from 2.14.0 to 4.13.0

[dependabot]

Bumps @prisma/client from 2.14.0 to 4.13.0.

Release notes

Sourced from @​prisma/client's releases.

4.13.0

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

Highlights

Introspection stopgaps

The Prisma Schema Language (PSL) currently doesn't support all database features and functionality of our target databases. The PSL is an abstraction over SQL and will keep evolving to address gaps in our database feature matrix.

Before this release, prisma db pull did not pick up the unsupported features in a database. It was easy to lose them when running prisma migrate dev based on an existing Prisma schema if not included in a migration file using custom migrations.

To avoid this, we added Introspection Stopgaps that surface the existence of these features in your database and link to our documentation on how to manually work around the Prisma Schema with unsupported database features (”Stopgaps” as we will remove them as soon as we implement full support for these features).

In this release, we added stopgaps for the following features:

• Partitioned tables
• PostgreSQL Row Level Security
• Index sort order, NULLS FIRST / NULLS LAST
• CockroachDB row-level TTL
• Comments
• PostgreSQL deferred constraints

Prisma CLI will output warnings on introspection (prisma db pull) and add comments to your Prisma schema. In the coming releases, we will expand this to many more features labeled with topic: database-functionality on GitHub.

Improved support for Netlify and Vercel build process

Netlify and Vercel cache project dependencies during the build process and reuse that cache until dependencies change. While this helps speed up the build process, any postinstall scripts of these dependencies will not be executed.

Prisma uses a postinstall script in its package to automatically trigger the customized generation of Prisma Client for your Prisma Schema. When a dependency cache is used, that generation process is not triggered, and an outdated Prisma Client may be used in your application.

When you update your Prisma Schema but not your dependencies, Prisma Client will not be generated for the new schema. For example, columns you added recently to one of your models will not be present in the Prisma Client API - causing errors.

This problem can be avoided by:

1. Adding a custom postinstall script in your package.json file
2. Manually adding a prisma generate step to the “Build” scripts of Vercel and Netlify.

We now added detection of this scenario and will prevent a build without an additional prisma generate. This will ensure you're aware of the problem early and get guidance on how to fix this problem. You can read more on how to do this in our docs — Vercel caching troubleshooting, Netlify caching troubleshooting.

Better support for pnpm as a package manager

Before this release, Prisma only used npm scripts which would lead to undesirable behavior for a project using a different package manager such as pnpm and yarn. This release improves the detection of the package managers in your project by using ni. If you're still running into this problem, let us know by creating a GitHub issue.

Segmentation fault and TLS connection error fix

In this release, we've fixed a TLS connection error segmentation fault. This mostly affected users running on Node.js 17 or later with OpenSSL 1.1 when using TLS to connect to their database.

JSON protocol Preview feature feedback

We have fixed multiple bugs for the jsonProtocol Preview feature and are close to making it Generally Available. We are still looking for feedback about its usage to ensure it is ready and works as expected for everyone.

... (truncated)

Commits

• d14eeff chore(deps): update engines to 4.13.0-50.1e7af066ee9cb95cf3a403c78d9aab3e6b04...
• 84af70e fix(client): add console error log for caching on top of error (#18759)
• f3c08d9 chore(deps): update engines to 4.13.0-42.745dcc4b3aa8b8a153cf4fa46478871befdf...
• c0334cf chore(client): Add test for #18598 and simplify serialization code (#18756)
• fcc6d00 chore(deps): update engines to 4.13.0-40.5a83cdfb84729117ca82344e1c7359783ded...
• d452662 fix(client, cli): client auto-install for pnpm (#18646)
• bf64679 chore(deps): update engines to 4.13.0-37.36b8399dd5f1338f3240a853c5ff70f98458...
• c6e615e chore(deps): update engines to 4.13.0-35.b7a219819742333ebd961a4511cbb4efd76a...
• 878c84f chore: fix eslint errors (#18587)
• 647bd20 chore(deps): update engines to 4.13.0-33.5af5b01cc5d77d6887ef748cf6b9564be909...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by prismabot, a new releaser for @​prisma/client since your current version.

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 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)