ghost
commented
1 year ago 👇 Click on the image for a new way to code review
#### [](https://app.codesee.io/r/reviews?pr=2600&src=https%3A%2F%2Fgithub.com%2FfreeCodeCamp%2Fchapter) #### Legend
This PR contains the following updates:
4.12.0->4.13.04.12.0->4.13.0Release Notes
prisma/prisma
### [`v4.13.0`](https://togithub.com/prisma/prisma/releases/tag/4.13.0) [Compare Source](https://togithub.com/prisma/prisma/compare/4.12.0...4.13.0) 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v4.13.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/4.13.0) about the release.** 🌟 ##### Highlights ##### Introspection stopgaps The Prisma Schema Language (PSL) currently doesn't support all database features and functionality of [our target databases](https://www.prisma.io/docs/reference/database-reference/supported-databases). The PSL is an abstraction over SQL and will keep evolving to address gaps in our [database feature matrix](https://www.prisma.io/docs/reference/database-reference/database-features). 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](https://togithub.com/prisma/prisma/issues/1708) - [PostgreSQL Row Level Security](https://togithub.com/prisma/prisma/issues/12735) - [Index sort order, `NULLS FIRST` / `NULLS LAST`](https://togithub.com/prisma/prisma/issues/15466) - [CockroachDB row-level TTL](https://togithub.com/prisma/prisma/issues/13982) - [Comments](https://togithub.com/prisma/prisma/issues/8703) - [PostgreSQL deferred constraints](https://togithub.com/prisma/prisma/issues/8807) 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](https://togithub.com/prisma/prisma/issues?q=is%3Aopen+label%3A%22topic%3A+database-functionality%22+label%3Ateam%2Fschema+sort%3Aupdated-desc+). ##### 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](https://prisma.io/docs/guides/other/troubleshooting-orm/help-articles/vercel-caching-issue), [Netlify caching troubleshooting](https://prisma.io/docs/guides/other/troubleshooting-orm/help-articles/netlify-caching-issue). ##### 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`](https://togithub.com/antfu/ni). If you're still running into this problem, let us know by creating a [GitHub issue](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&template=bug_report.yml). ##### 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. We would appreciate it if you would try it out, help us polish the feature, and move it to General Availability. Testing it requires little effort. You can test it using the following steps: 1. Enabling the `jsonProtocol` Preview feature in your Prisma schema 2. Re-generating Prisma Client 3. Running your application or tests to make sure everything works We encourage you to leave your feedback in [this GitHub issue](https://togithub.com/prisma/prisma/issues/18095) or [create a bug report](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&template=bug_report.yml) if your run into any issues. ##### Fixes and improvements ##### Prisma Client - [`prisma generate` fails when using pnpm workspaces because it tries to install prisma dependencies with npm or yarn](https://togithub.com/prisma/prisma/issues/5340) - [Netlify deploy does not pick up changes to schema file](https://togithub.com/prisma/prisma/issues/6634) - [Vercel: Schema only change does not invalidate build cache](https://togithub.com/prisma/prisma/issues/7291) - [Serverless deployments: Just making a schema level change to a repository does not invalidate `node_modules` cache that contains generated Client](https://togithub.com/prisma/prisma/issues/7818) - [pnpm: Can not `prisma generate` when `@prisma/client` is not installed in project](https://togithub.com/prisma/prisma/issues/9848) - [Segmentation fault crash when using prisma client when using PostgreSQL](https://togithub.com/prisma/prisma/issues/10649) - [Docker with `pnpm install` hangs on `@prisma/client` postinstall ](https://togithub.com/prisma/prisma/issues/11791) - [Automatic installation of missing dependencies isn't compatible with pnpm](https://togithub.com/prisma/prisma/issues/14401) - [Prisma generate throws dependency error karma-chai](https://togithub.com/prisma/prisma/issues/14816) - [Postinstall script fails with PNPM workspaces due to npm ERR! Cannot read properties of null (reading 'matches')](https://togithub.com/prisma/prisma/issues/14944) - [Debian 11 Node 19.3.0 segmentation fault](https://togithub.com/prisma/prisma/issues/16897) - [Prisma client segfault on Ubuntu 22.04](https://togithub.com/prisma/prisma/issues/17223) - [Segmentation Fault in Postgres](https://togithub.com/prisma/prisma/issues/17946) - [Using Prisma with pnpm results in inability to call database related commands](https://togithub.com/prisma/prisma/issues/18238) - [Prisma Connect Causes NodeJS to Close With Exit Code 0](https://togithub.com/prisma/prisma/issues/18336) - [99056 segmentation fault (core dumped) node --require esbuild-register prisma/seed.ts](https://togithub.com/prisma/prisma/issues/18559) - [JSON protocol: sibling composites of the same type are rejected](https://togithub.com/prisma/prisma/issues/18735) ##### Prisma Migrate - [prisma db pull adds redundant comments: "This table is a partition table ..."](https://togithub.com/prisma/prisma/issues/18103) - [Render warning code 30 in cli (PG RLS)](https://togithub.com/prisma/prisma/issues/18700) ##### Language tools (e.g. VS Code) - [`[object Object]` output in logging isn't helpful](https://togithub.com/prisma/language-tools/issues/1390) ##### Credits Huge thanks to [@KhooHaoYit](https://togithub.com/KhooHaoYit), [@rintaun](https://togithub.com/rintaun), [@maxmartynov](https://togithub.com/maxmartynov), [@haneenmahd](https://togithub.com/haneenmahd) for helping! ##### 📺 Join us for another "What's new in Prisma" live stream Learn about the latest release and other news from the Prisma community by joining us for another ["What's new in Prisma"](https://youtube.com/playlist?list=PLn2e1F9Rfr6l1B9RP0A9NdX7i7QIWfBa7) live stream. The stream takes place [on YouTube](https://youtu.be/NXzQIkfF3E8) on **Thursday, April 20** at **5 pm Berlin | 8 am San Francisco**.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.