Bump @prisma/client from 5.10.1 to 5.15.0

dependabot[bot] commented 1 month ago

Bumps @prisma/client from 5.10.1 to 5.15.0.

Release notes

Sourced from @prisma/client's releases.

5.15.0

Today, we are excited to share the 5.15.0 stable release 🎉

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

Highlights

Multi-File Prisma Schema support

Prisma ORM 5.15.0 features support for multi-file Prisma Schema in Preview.

This closes a long standing issue and does so in a clean and easy to migrate way.

To get started:
Enable the prismaSchemaFolder Preview feature by including it in the previewFeatures field of your generator.
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}
generator client {
provider        = "prisma-client-js"
previewFeatures = ["prismaSchemaFolder"]
}
Create a schema subdirectory under your prisma directory.

Move your schema.prisma into this directory.
You are now set up with a multi-file Prisma Schema! Add as many or as few .prisma files to the new prisma/schema directory.

When running commands where a Prisma Schema file is expected to be provided, you can now define a Prisma Schema directory. This includes Prisma CLI commands that use the --schema option as well as defining schema via package.json

Our tooling has also been updated to handle multiple Prisma Schema files. This includes our Visual Studio Code extension and tools like database introspection, which will deposit new models in a introspected.prisma file. Existing models will be updated in the file they are found.

To learn more, please refer to our official documentation and announcement blog post. If you try out prismaSchemaFolder, please let us know!

Interesting Bug Fixes

Fix for PostgreSQL prepared statement caching for raw queries

This release fixes a nasty bug with the caching of prepared statements in raw Prisma Client queries that affected PostgreSQL when you ran the same SQL statement with differently typed paramters. This should not fail any more.

Fix for SQL Server introspection of (deprecated) CREATE DEFAULT

Our Introspection logic crashed on encountering certain multi-line CREATE DEFAULT, a deprecated way to define defaults in SQL Server. As many SQL Server users are working with established databases, this happened frequently enough that we now explicitly ignore these defaults instead of crashing.

Fix for Cloudflare D1’s lower parameter limit

... (truncated)

Commits

9dc475c chore(tests): Remove providerFeatures from functional test example and docs...
a39c5b9 chore(deps): update engines to 5.15.0-29.12e25d8d06f6ea5a0252864dd9a03b1bb51f...
1d00bdd chore(deps): update engines to 5.15.0-28.7320bfae295254d9b1fefc5030ff162143c7...
3b3d0c9 fix(adapter-d1): maxBoundValues (#24393)
a7bc5b9 chore(deps): update dependency @libsql/client to v0.6.2 (#24391)
f3e827c chore(deps): update dependency wrangler to v3.58.0 (#24384)
d2beef0 chore(deps): update engines to 5.15.0-27.d99d360a45b6c8582f83deadf81b73054afa...
79de5cf chore(deps): update dependency @swc/core to v1.5.24 (#24364)
d781e87 feat(migrate): Add split schema support to db pull (#24337)
729c664 chore(deps): update dependency @libsql/client to v0.6.1 (#24363)
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)

vercel[bot] commented 1 month ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sharrr-svelte	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 5, 2024 10:05am

socket-security[bot] commented 1 month ago

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note
Install scripts	npm/@prisma/client@5.10.1	Install script: postinstall Source: `node scripts/postinstall.js`

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/@prisma/client@5.10.1

dependabot[bot] commented 2 weeks ago

Superseded by #236.

stophecom / sharrr-svelte