[Snyk] Upgrade prisma from 4.15.0 to 4.16.0 #23

GreenyDEV · 2023-07-12T04:02:01Z

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

Snyk has created this PR to upgrade prisma from 4.15.0 to 4.16.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 164 versions ahead of your current version.
The recommended version was released 22 days ago, on 2023-06-20.

Release notes

Package name: prisma

4.16.0 - 2023-06-20
Read more
4.16.0-integration-studio-xdg-enoent.1 - 2023-06-16
4.16.0-integration-studio-direct-url.6 - 2023-06-03
4.16.0-integration-studio-direct-url.5 - 2023-06-03
4.16.0-integration-studio-direct-url.4 - 2023-06-03
4.16.0-integration-studio-direct-url.3 - 2023-06-03
4.16.0-integration-studio-direct-url.2 - 2023-06-03
4.16.0-integration-studio-direct-url.1 - 2023-06-02
4.16.0-integration-remove-openssl-fallback.2 - 2023-06-14
4.16.0-integration-remove-openssl-fallback.1 - 2023-06-14
4.16.0-integration-prisma5.1 - 2023-06-07
4.16.0-integration-node-drivers-prisma-playground.7 - 2023-06-16
4.16.0-integration-node-drivers-prisma-playground.6 - 2023-06-15
4.16.0-integration-node-drivers-prisma-playground.5 - 2023-06-15
4.16.0-integration-node-drivers-prisma-playground.4 - 2023-06-15
4.16.0-integration-node-drivers-prisma-playground.3 - 2023-06-15
4.16.0-integration-node-drivers-prisma-playground.2 - 2023-06-14
4.16.0-integration-node-drivers-prisma-playground.1 - 2023-06-13
4.16.0-integration-node-drivers.1 - 2023-06-07
4.16.0-integration-linux-static.5 - 2023-06-16
4.16.0-integration-linux-static.4 - 2023-06-16
4.16.0-integration-linux-static.3 - 2023-06-16
4.16.0-integration-linux-static.2 - 2023-06-16
4.16.0-integration-linux-static.1 - 2023-06-16
4.16.0-integration-fix-client-extension-never-type.2 - 2023-06-05
4.16.0-integration-fix-client-extension-never-type.1 - 2023-06-05
4.16.0-integration-engines-4-16-0-73-cockroachdb-with-postgres-provider-e3806492ee9cd6d784cfb440ea5b4ffa412ae635.1 - 2023-06-20
4.16.0-integration-engines-4-16-0-72-integration-support-arrays-generator-config-d181c89134a5f9e48a42e6d90be0b3da518c6236.1 - 2023-06-20
4.16.0-integration-engines-4-16-0-71-cockroachdb-with-postgres-provider-5dbcd575dfeb408cbd8d423edb813cf42606c8bb.1 - 2023-06-20
4.16.0-integration-engines-4-16-0-70-integration-tracing-runtime-js-b967cfe0b3471cb83685e28c9bbccd0a25180ce6.1 - 2023-06-19
4.16.0-integration-engines-4-16-0-69-integration-tracing-runtime-js-5640e37d36a967a91e3a56eaf0a8afbef0ffdcb8.1 - 2023-06-17
4.16.0-integration-engines-4-16-0-68-integration-tracing-runtime-js-12b7801a1233c86e4a4ba00f600a19193dbe0255.1 - 2023-06-16
4.16.0-integration-engines-4-16-0-67-integration-tracing-runtime-js-7aa3bfc9131f8e5f9bfa0b2aeed94806dd65cbfc.1 - 2023-06-16
4.16.0-integration-engines-4-16-0-65-integration-default-protocol-a001640fb1246b05489d399bc4d41dfd2c74f342.1 - 2023-06-16
4.16.0-integration-engines-4-16-0-64-integration-linux-static-4dd629bf84f12f4770c3b6877d20c45d8d0933f1.1 - 2023-06-16
4.16.0-integration-engines-4-16-0-63-integration-tracing-runtime-js-9f7de8712f7653c6264679213b3c779d11e2dc28.1 - 2023-06-16
4.16.0-integration-engines-4-16-0-62-integration-tracing-runtime-js-dd2821c098a7360794afae9efa80a43abfbd4b73.1 - 2023-06-16
4.16.0-integration-engines-4-16-0-61-integration-default-protocol-05dbc451f077f23c3a09370aeb37d65841e18c45.1 - 2023-06-16
4.16.0-integration-engines-4-16-0-58-integration-default-protocol-39a634853d3c50aab9140ba300ac71d7a923cb5d.1 - 2023-06-16
4.16.0-integration-engines-4-16-0-57-integration-linux-static-a156add034f679923521d232012267423a49deb3.1 - 2023-06-15
4.16.0-integration-engines-4-16-0-55-integration-node-drivers-naming-consistency-34882a922df80c18cdc4d8165413e6e5bfa92be2.1 - 2023-06-15
4.16.0-integration-engines-4-16-0-54-integration-node-drivers-naming-consistency-dd29c78f0214ca7b313018a3249d6da9bab8310b.1 - 2023-06-15
4.16.0-integration-engines-4-16-0-52-integration-node-drivers-naming-consistency-a422ada172398518dbda4b173d5cd48de33a7361.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-51-integration-node-drivers-naming-consistency-6eabdcbccb2f2594fbdd94f96fd4abb3181512c2.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-50-integration-node-drivers-typed-ba4ec9e7ca19c51b567950aa6280a254618fec3c.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-47-integration-node-drivers-with-types-and-no-missing-symbols-0c1cc1c08f0434bd4e8d7a611764c704f1d3d036.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-46-integration-node-drivers-typed-3bd373d936cdd25f9999443d99a838fa1f6fee40.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-45-integration-node-drivers-with-types-and-no-missing-symbols-0c1cc1c08f0434bd4e8d7a611764c704f1d3d036.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-44-integration-improve-field-ref-validation-8c84ff041eeab5d2e363bfa413319df8dff57317.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-43-integration-node-drivers-typed-d38ce960a0e364072c6353ff74d16a6c8a273e1e.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-40-integration-node-drivers-typed-bc749c86dc6fb47ac88bc809cb855c7233464b29.1 - 2023-06-14
4.16.0-integration-engines-4-16-0-38-integration-node-drivers-typed-nonverbose-81afb6281350299d232ca0216ea77874926fb2a5.1 - 2023-06-13
4.16.0-integration-engines-4-16-0-36-integration-node-drivers-typed-5d66c7e6ec24ec039f62ef5e17372a96a1f87a3c.1 - 2023-06-13
4.16.0-integration-engines-4-16-0-34-integration-node-drivers-typed-a47f6564408b5ed5dc3fe47a1e62b31ea5e7cfb7.1 - 2023-06-13
4.16.0-integration-engines-4-16-0-33-integration-node-drivers-typed-85df2668765479cf818507da0275ab374c55e1e9.1 - 2023-06-13
4.16.0-integration-engines-4-16-0-32-integration-node-drivers-typed-25ee6cdf9b1572d809e11912d477a36137fa8e74.1 - 2023-06-13
4.16.0-integration-engines-4-16-0-30-integration-node-drivers-typed-dcbf645a1b3d70873571a18df2385f1cadb4b6d8.1 - 2023-06-12
4.16.0-integration-engines-4-16-0-3-integration-engineer-optimization-tests-ed188a18e0fafd8565c18baef3532f0d6822f2c7.1 - 2023-05-30
4.16.0-integration-engines-4-16-0-29-integration-standardise-targets-afe4fa3b8c57711182fffa9d89332774db3b7f8f.1 - 2023-06-12
4.16.0-integration-engines-4-16-0-28-integration-improve-field-ref-validation-2357b35a6b2132dc3ae7d43c05aac5d415bbb319.1 - 2023-06-12
4.16.0-integration-engines-4-16-0-27-integration-node-drivers-typed-ccc06a75e230d74f9fddcccf58068531b96bbdde.1 - 2023-06-12
4.16.0-integration-engines-4-16-0-25-integration-node-drivers-typed-e5ed83cfc47e5929203654cbdf52c5f31b7e7062.1 - 2023-06-12
4.16.0-integration-engines-4-16-0-24-integration-support-arrays-generator-config-f359e6c1e8593b12c52e4000babe77cdd7a66300.1 - 2023-06-09
4.16.0-integration-engines-4-16-0-23-integration-node-drivers-typed-45573408cca611fc19c003755e5348a127d9f147.1 - 2023-06-09
4.16.0-integration-engines-4-16-0-22-integration-node-drivers-typed-65b6d81f12965f9ef6ac3df907e435d49c0c285c.1 - 2023-06-09
4.16.0-integration-engines-4-16-0-21-integration-node-drivers-typed-49c3279792632f97a8f9f76330445640a49dcec0.1 - 2023-06-09
4.16.0-integration-engines-4-16-0-20-integration-improve-field-ref-validation-238ecf6c8d3482d7d27517872e056014a2742297.1 - 2023-06-09
4.16.0-integration-engines-4-16-0-2-integration-engineer-optimization-tests-2aeb9bd9dce49766ec608374164fd84dc031577a.1 - 2023-05-30
4.16.0-integration-engines-4-16-0-19-integration-only-upload-to-all-commits-85e190cf5d4e54af3674e0367921657166a4b7e0.1 - 2023-06-08
4.16.0-integration-engines-4-16-0-18-integration-improve-field-ref-validation-ee7d4c6785824887c53e392b87b1915c5f2b4c93.1 - 2023-06-08
4.16.0-integration-engines-4-16-0-16-integration-rename-migration-engine-to-schema-engine-72a818438fbeb692961516daebf61ab86af03011.1 - 2023-06-07
4.16.0-integration-engines-4-16-0-15-integration-node-drivers-c750faaec2e560cab1a3eeac4bf8e6cc17bf5b8c.1 - 2023-06-07
4.16.0-integration-engines-4-16-0-14-integration-node-drivers-fix-nix-4b8d8a2efc3efe19ac4f52f9de699857a3a0257f.1 - 2023-06-07
4.16.0-integration-engines-4-16-0-10-integration-linux-static-70a9adfd11f836696eca398396544fe07a8d8edb.1 - 2023-06-01
4.16.0-integration-dont-generate-package-json.10 - 2023-06-19
4.16.0-integration-dont-generate-package-json.9 - 2023-06-19
4.16.0-integration-dont-generate-package-json.8 - 2023-06-19
4.16.0-integration-dont-generate-package-json.7 - 2023-06-19
4.16.0-integration-dont-generate-package-json.6 - 2023-06-16
4.16.0-integration-dont-generate-package-json.5 - 2023-06-15
4.16.0-integration-dont-generate-package-json.4 - 2023-06-15
4.16.0-integration-dont-generate-package-json.3 - 2023-06-15
4.16.0-integration-dont-generate-package-json.2 - 2023-06-15
4.16.0-integration-dont-generate-package-json.1 - 2023-06-14
4.16.0-integration-chore-remove-detection-fallback.2 - 2023-06-14
4.16.0-integration-chore-remove-detection-fallback.1 - 2023-06-14
4.16.0-integration-bench.1 - 2023-06-02
4.16.0-dev.78 - 2023-06-20
4.16.0-dev.77 - 2023-06-19
4.16.0-dev.76 - 2023-06-19
4.16.0-dev.75 - 2023-06-19
4.16.0-dev.74 - 2023-06-16
4.16.0-dev.73 - 2023-06-16
4.16.0-dev.72 - 2023-06-16
4.16.0-dev.71 - 2023-06-16
4.16.0-dev.70 - 2023-06-16
4.16.0-dev.69 - 2023-06-16
4.16.0-dev.68 - 2023-06-16
4.16.0-dev.67 - 2023-06-16
4.16.0-dev.66 - 2023-06-16
4.16.0-dev.65 - 2023-06-16
4.16.0-dev.64 - 2023-06-15
4.16.0-dev.63 - 2023-06-15
4.16.0-dev.62 - 2023-06-15
4.16.0-dev.61 - 2023-06-15
4.16.0-dev.60 - 2023-06-15
4.16.0-dev.59 - 2023-06-15
4.16.0-dev.58 - 2023-06-15
4.16.0-dev.57 - 2023-06-14
4.16.0-dev.56 - 2023-06-14
4.16.0-dev.55 - 2023-06-14
4.16.0-dev.54 - 2023-06-14
4.16.0-dev.53 - 2023-06-14
4.16.0-dev.52 - 2023-06-14
4.16.0-dev.51 - 2023-06-14
4.16.0-dev.50 - 2023-06-14
4.16.0-dev.49 - 2023-06-13
4.16.0-dev.48 - 2023-06-13
4.16.0-dev.47 - 2023-06-13
4.16.0-dev.45 - 2023-06-13
4.16.0-dev.44 - 2023-06-13
4.16.0-dev.43 - 2023-06-12
4.16.0-dev.42 - 2023-06-12
4.16.0-dev.41 - 2023-06-12
4.16.0-dev.40 - 2023-06-12
4.16.0-dev.39 - 2023-06-12
4.16.0-dev.38 - 2023-06-12
4.16.0-dev.37 - 2023-06-09
4.16.0-dev.36 - 2023-06-09
4.16.0-dev.35 - 2023-06-08
4.16.0-dev.34 - 2023-06-08
4.16.0-dev.33 - 2023-06-08
4.16.0-dev.32 - 2023-06-08
4.16.0-dev.31 - 2023-06-07
4.16.0-dev.30 - 2023-06-07
4.16.0-dev.29 - 2023-06-07
4.16.0-dev.28 - 2023-06-07
4.16.0-dev.27 - 2023-06-07
4.16.0-dev.26 - 2023-06-07
4.16.0-dev.25 - 2023-06-06
4.16.0-dev.24 - 2023-06-06
4.16.0-dev.23 - 2023-06-05
4.16.0-dev.22 - 2023-06-05
4.16.0-dev.21 - 2023-06-05
4.16.0-dev.20 - 2023-06-05
4.16.0-dev.19 - 2023-06-05
4.16.0-dev.18 - 2023-06-05
4.16.0-dev.17 - 2023-06-05
4.16.0-dev.16 - 2023-06-05
4.16.0-dev.15 - 2023-06-05
4.16.0-dev.14 - 2023-06-02
4.16.0-dev.13 - 2023-06-02
4.16.0-dev.12 - 2023-06-02
4.16.0-dev.11 - 2023-06-02
4.16.0-dev.10 - 2023-06-02
4.16.0-dev.9 - 2023-06-02
4.16.0-dev.8 - 2023-06-01
4.16.0-dev.7 - 2023-06-01
4.16.0-dev.6 - 2023-06-01
4.16.0-dev.5 - 2023-05-31
4.16.0-dev.4 - 2023-05-30
4.16.0-dev.3 - 2023-05-30
4.16.0-dev.2 - 2023-05-30
4.16.0-dev.1 - 2023-05-30
4.15.0 - 2023-05-30
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

For this release, we focused on fixing bugs and making smaller quality-of-life improvements.

Support for custom arguments for prisma db seed

This release adds support for defining and passing arbitrary arguments to prisma db seed. This creates the opportunity for you to define your own arguments in your seed file that you could pass to the prisma db seed command. A few example use-cases include, but are not limited to:
- Seeding different data in different environments
- Partially seeding data in some tables
Here is an example seed.ts file that defines custom arguments for seeding different data in different environments:

// prisma/seed.ts
import { parseArgs } from "node:util";

const options = {
environment: { type: 'string', },
}

async function main() {
const { values: { environment } } = parseArgs({ options })

switch (environment) {
case "development":
/** do something for development /
break;
case "test":
/* do something for test environment */
break;
default:
break;
}
}

main()

You can then provide the environment argument when executing the seed script as follows:
```
npx prisma db seed -- --environment development
```
Let us know what you think, share example usage of this feature, and create a bug report if you run into any issues.

Improved error messages when Query Engine file is not found

This release improves the error messages returned by Prisma Client when the Query Engine file is not found. A few reasons the Query Engine file might be missing from your application bundle include when:
- The downloaded Query Engine doesn’t match the runtime/ target platform your application is running on.
- The Query Engine is not copied to your final application bundle during the build step.
We hope these error messages are helpful while debugging your application.

Prisma VS Code extension improvements

In this release, we made a few improvements to our VS Code extension:
1. Updated the file system watcher that is responsible for restarting the TypeScript server when prisma generate is run to ensure the types are in sync
  Note:
  - This new approach is currently only available on Windows and Linux. We plan on adding support for the new file system watcher on macOS soon.
  - This requires both Prisma CLI & VS code extension version 4.15.0 or higher
2. Added Quick Fixes action for unique identifiers for MongoDB to add the @ map("_id") attribute function when it’s missing on an identifier field
  
  Screen.Recording.2023-05-17.at.19.22.20.mov
  
  Screen.Recording.2023-05-17.at.19.22.20.mov
3. Support for renaming symbols for composite types and views
  
  type-symbol-rename.mov
  
  type-symbol-rename.mov
Fixes and improvements

Prisma Client
- Prisma generate - Error: write EPIPE on WSL <-> Windows
- prisma generate is blocked by query-engine-rhel-openssl-1.0.x opening in Notepad on Windows
- Generated client output path hardcoded to build environment
- Issue with Yarn Workspace Monorepo: Query engine binary for current platform could not be found.
- Cloning a project with checked in node_modules (from another platform) leads to platform engine not being present
- SvelteKit, Vite and Prisma "module not defined"
- Schema File Not Found in non monorepo with custom output
- Deploying to Cloudflare Workers | "PrismaClient is unable to be run in the browser"
- Inline/bundle the contents of the prisma schema on generate
- Netlify: Query engine library for current platform "rhel-openssl-1.0.x" could not be found. You incorrectly pinned it to rhel-openssl-1.0.x
- Query Engine Library Not Found
- No client schema when using PrismaClient during cached (standard) Netlify build
- Module "@ prisma/client" has no exported member "PrismaClient"
- EPERM: operation not permitted
- prisma/client crashes when used with older versions of react-refresh
- Unable to run prisma cli in pnpm monorepo from workspace install
- Misleading error message when the query engine is not found
- When setting custom client output directory, generated package.json does not include "sideEffects: false"
- You already added the platform "debian-openssl-1.1.x" to the "generator" block in the "schema.prisma" file as described in https://pris.ly/d/client-generator, but something went wrong.
- Prisma seems to be looking in the wrong location for rhel-openssl-1.0.x
- Can't find prisma engine
- Cannot find name '$PrismaModel' due to feature extendedWhereUnique with preview feature fieldReference
- Netlify build fails with PrismaClientInitializationError
- i'm getting the error while requesting the api
- Query engine library for current platform could not be found.
- Prisma unable to reconnect if initial connection fails
- GraphQL protocol encoder incorrectly turns empty array into empty object.
- GraphQL protocol: Invalid Date values silently turn into nulls
- @prisma/client/edge + Cloudflare Worker / wrangler = Could not resolve "os"
- Client is bricked from connecting to DB if first attempt fails.
- JSON protocol: incorrect recursive composites detection through multiple nesting levels
- fieldReference is not working with enums
Prisma Migrate
- Pass extra arguments to prisma db seed to the seed command
- Typo in generating migration SQL to add enum.
Language tools (e.g. VS Code)
- MongoDB: Quick fix for missing @ map("_id") annotation
- Rename composite types
- Views: Support for rename
- TextDocument deprecation
- Lib name change vsce -> @ vscode/vsce
Credits

Huge thanks to @ RobertCraigie, @ KhooHaoYit, @ art049, @ luxaritas, @ mrazauskas, @ maxmartynov, @ 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" live stream.

The stream takes place on YouTube on Thursday, June 1 at 5 pm Berlin | 8 am San Francisco.