Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update prisma monorepo to v5.15.1 #10857

Merged
merged 1 commit into from
Jun 19, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 18, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) 5.14.0 -> 5.15.1 age adoption passing confidence
@prisma/internals (source) 5.14.0 -> 5.15.1 age adoption passing confidence
prisma (source) 5.14.0 -> 5.15.1 age adoption passing confidence

Release Notes

prisma/prisma (@​prisma/client)

v5.15.1

Compare Source

Today, we are issuing the 5.15.1 patch release.

Fixes in Prisma Client

v5.15.0

Compare Source

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:

  1. 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"]
    }
    
  2. Create a schema subdirectory under your prisma directory.
  3. 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

Cloudflare’s D1 has a lower parameter limit than local SQLite, which caused bigger queries to fail. We adapted that limit to the D1 default for @prisma/adapter-d1, which will avoid such failures.

Fix for Cloudflare D1’s different PRAGMA support

Our generated migration SQL for SQLite did not always work for Cloudflare D1, because of differences in the supported pragmas. We adapted the SQL to work in both local SQLite and Cloudflare D1.

Fixes and improvements
Prisma Migrate
Prisma Client
Language tools (e.g. VS Code)
Credits

Huge thanks to @​pranayat, @​yubrot, and @​skyzh for helping!


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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Sorry, something went wrong.

@renovate renovate bot enabled auto-merge (squash) June 18, 2024 23:37
@Josh-Walker-GM Josh-Walker-GM added this to the next-release milestone Jun 18, 2024
@Josh-Walker-GM Josh-Walker-GM added release:chore This PR is a chore (means nothing for users) changesets-ok Override the changesets check labels Jun 18, 2024
@renovate renovate bot merged commit e701712 into main Jun 19, 2024
54 of 61 checks passed
@renovate renovate bot deleted the renovate/prisma-monorepo branch June 19, 2024 00:18
Josh-Walker-GM pushed a commit that referenced this pull request Jun 25, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@prisma/client](https://www.prisma.io)
([source](https://github.com/prisma/prisma/tree/HEAD/packages/client))
| [`5.14.0` ->
`5.15.1`](https://renovatebot.com/diffs/npm/@prisma%2fclient/5.14.0/5.15.1)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@prisma%2fclient/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@prisma%2fclient/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@prisma%2fclient/5.14.0/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@prisma%2fclient/5.14.0/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [@prisma/internals](https://www.prisma.io)
([source](https://github.com/prisma/prisma/tree/HEAD/packages/internals))
| [`5.14.0` ->
`5.15.1`](https://renovatebot.com/diffs/npm/@prisma%2finternals/5.14.0/5.15.1)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@prisma%2finternals/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@prisma%2finternals/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@prisma%2finternals/5.14.0/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@prisma%2finternals/5.14.0/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [prisma](https://www.prisma.io)
([source](https://github.com/prisma/prisma/tree/HEAD/packages/cli)) |
[`5.14.0` ->
`5.15.1`](https://renovatebot.com/diffs/npm/prisma/5.14.0/5.15.1) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/prisma/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/prisma/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/prisma/5.14.0/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/prisma/5.14.0/5.15.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

<details>
<summary>prisma/prisma (@&#8203;prisma/client)</summary>

[Compare
Source](https://github.com/prisma/prisma/compare/5.15.0...5.15.1)

Today, we are issuing the `5.15.1` patch release.

- [internal error: entered unreachable
code](https://github.com/prisma/prisma/issues/23407)
- [Got error 'internal error: entered unreachable code' when trying to
perform an upsert.](https://github.com/prisma/prisma/issues/22947)
- [Prisma Client errors on SQLite with internal error: entered
unreachable code when running 2 concurrent upsert
](https://github.com/prisma/prisma/issues/22725)
- [`ConnectionError(Timed out during query execution.)` during
seeding](https://github.com/prisma/prisma/issues/21772)
- [SQLite timeouts after upgrade from prisma 2 to prisma
4](https://github.com/prisma/prisma/issues/17029)
- [`ConnectionError(Timed out during query execution.)` error when using
`Promise.all` for
SQLite](https://github.com/prisma/prisma/issues/11789)
- [Improve the error when SQLite database file is
locked](https://github.com/prisma/prisma/issues/10403)
- [sqlite timeout error multiple queries run one after
another](https://github.com/prisma/prisma/issues/10306)
- [SQLite times out during query execution when using `Promise.all()` /
concurrent](https://github.com/prisma/prisma/issues/9562)
- [internal error: entered unreachable
code](https://github.com/prisma/prisma/issues/24511)

[Compare
Source](https://github.com/prisma/prisma/compare/5.14.0...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](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@&#8203;prisma%20release%20v5.15.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.15.0)
about the release.** 🌟

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

This closes [a long standing
issue](https://github.com/prisma/prisma/issues/2377) and does so in a
clean and easy to migrate way.

To get started:

1. Enable the `prismaSchemaFolder` Preview feature by including it in
the `previewFeatures` field of your `generator`.
    ```prisma
    datasource db {
      provider = "postgresql"
      url      = env("DATABASE_URL")
    }

    generator client {
      provider        = "prisma-client-js"
      previewFeatures = ["prismaSchemaFolder"]
    }

    ```
2.  Create a `schema` subdirectory under your `prisma` directory.
3.  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](https://www.prisma.io/blog/organize-your-prisma-schema-with-multi-file-support).
If you try out `prismaSchemaFolder`, please [let us
know](https://github.com/prisma/prisma/discussions/24413)!

This release fixes a [nasty bug with the caching of prepared
statements](https://github.com/prisma/prisma/issues/22482) in [raw
Prisma Client
queries](https://www.prisma.io/docs/orm/prisma-client/queries/raw-database-access/raw-queries)
that affected PostgreSQL when you ran the same SQL statement with
differently typed paramters. This should not fail any more.

DEFAULT`**

Our Introspection logic
[crashed](https://github.com/prisma/prisma/issues/24275) on
encountering certain multi-line `CREATE DEFAULT`, a [deprecated way to
define defaults in SQL
Server](https://learn.microsoft.com/en-us/sql/t-sql/statements/create-default-transact-sql?view=sql-server-ver15).
As many SQL Server users are working with established databases, this
happened frequently enough that we now explicitly ignore these defaults
instead of crashing.

Cloudflare’s D1 has a lower parameter limit than local SQLite, which
caused [bigger queries to
fail](https://github.com/prisma/prisma/issues/23743). We adapted that
limit to the D1 default for `@prisma/adapter-d1`, which will avoid such
failures.

Our generated migration SQL for SQLite [did not always work for
Cloudflare D1](https://github.com/prisma/prisma/issues/24208), because
of differences in the supported pragmas. We adapted the SQL to work in
both local SQLite and Cloudflare D1.

- [Crash on multiline defaults introspection on
MSSQL](https://github.com/prisma/prisma/issues/10123)
- [Error: \[libs\sql-schema-describer\src\mssql.rs:315:30\] called
`Result::unwrap()` on an `Err` value: "Couldn't parse default value:
`create default [dbo].[member_notification_cancel_flags] as 0\r\n`"
](https://github.com/prisma/prisma/issues/10740)
- [Error: \[libs\sql-schema-describer\src\mssql.rs:315:30\] called
`Result::unwrap()` on an `Err` value: "Couldn't parse default value: `
create default d_password as 'D,73' `"
](https://github.com/prisma/prisma/issues/11010)
- [Crash introspecting MSSQL database with
`DEFAULT`s](https://github.com/prisma/prisma/issues/11557)
- [doing introspection on a SQL Server 2018 DB - for Dynamic GP get the
following error.](https://github.com/prisma/prisma/issues/14200)
- [Error: \[libs\sql-schema-describer\src\mssql.rs:317:30\] called
`Result::unwrap()` on an `Err` value: "Couldn't parse default value:
`\r\ncreate default D_BIT_OFF\r\nas 0\r\n`"
](https://github.com/prisma/prisma/issues/15704)
- [Error: called `Result::unwrap()` on an `Err` value: "Couldn't parse
default value in SQL
Server](https://github.com/prisma/prisma/issues/17069)
- [db pull errors on SQL Server with ` Error:
[libs\sql-schema-describer\src\mssql.rs:336:30] called
`Result::unwrap()`on an`Err` value: "Couldn't parse default value: [...]
`](https://github.com/prisma/prisma/issues/17104)
- [Error: \[libs\sql-schema-describer\src\mssql.rs:336:30\] called
`Result::unwrap()` on an `Err` value: "Couldn't parse default value:
`\r\ncreate default [va_nulla] as 0\r\n`"
](https://github.com/prisma/prisma/issues/17292)
- [Error when pulling from
database](https://github.com/prisma/prisma/issues/19971)
- [Foreign key relation results in erroneous second
migration](https://github.com/prisma/prisma/issues/23043)
- [`db pull` can't parse script setting default
value](https://github.com/prisma/prisma/issues/23453)
- [Bug: Migrations not compatible with
D1](https://github.com/prisma/prisma/issues/24208)
- [SQL Server Introspection crashes on multi-line (deprecated)
defaults](https://github.com/prisma/prisma/issues/24275)

- [Raw query failed. Code: `22P03`. Message: `db error: ERROR: incorrect
binary data format in bind parameter
1`](https://github.com/prisma/prisma/issues/16611)
- [Float number on raw query: `incorrect binary data format in bind
parameter 1`](https://github.com/prisma/prisma/issues/17110)
- [Can't use Prisma client in Next.js middleware, even when deploying to
Node.js](https://github.com/prisma/prisma/issues/21310)
- [Prepared statement caching is data dependent on numeric input
parameters (`incorrect binary data format in bind parameter
x`)](https://github.com/prisma/prisma/issues/22482)
- [Turso Driver Adapter: Including `_count` leads to
error](https://github.com/prisma/prisma/issues/23566)
- [Next.js app build fails when using Prisma with DB driver in Server
Action](https://github.com/prisma/prisma/issues/23600)
- [Bug: \[D1\] Error in performIO: Error: D1\_ERROR: too many SQL
variables](https://github.com/prisma/prisma/issues/23743)
- [Remove `warn(prisma-client) This is the 10th instance of Prisma
Client being started.` warning in Edge (and potentially) other
envs)](https://github.com/prisma/prisma/issues/23763)
- [$executeRawUnsafe: `incorrect binary data format in bind parameter
6`](https://github.com/prisma/prisma/issues/23872)
- [Bug: Error or bug using Prisma with DriverAdapter with PostgreSQL
database Neon](https://github.com/prisma/prisma/issues/23903)
- [`Inconsistent column data: Unexpected conversion failure from Number
to BigInt` error when using `@prisma/adapter-pg`
](https://github.com/prisma/prisma/issues/23926)
- [Incompatibility with NextJS app dir, CloudFlare Pages and
D1](https://github.com/prisma/prisma/issues/23929)
- [Breaking change? `Int` switched to being `Int32` for
MongoDB](https://github.com/prisma/prisma/issues/24262)

- [VS Code extension is showing an
advertisement](https://github.com/prisma/language-tools/issues/1732)
- [`Generate` codelens fails on
Windows](https://github.com/prisma/language-tools/issues/1738)
- [We incorrectly read commented out preview features if they are before
the real preview
features](https://github.com/prisma/language-tools/issues/1741)

Huge thanks to [@&#8203;pranayat](https://github.com/pranayat),
[@&#8203;yubrot](https://github.com/yubrot), and
[@&#8203;skyzh](https://github.com/skyzh) for helping!

</details>

---

📅 **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.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/redwoodjs/redwood).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTAuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQxMC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@Josh-Walker-GM Josh-Walker-GM added release:dependency This PR only updates dependencies and removed release:chore This PR is a chore (means nothing for users) labels Jul 31, 2024
@Josh-Walker-GM Josh-Walker-GM modified the milestones: next-release, v8.0.0 Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changesets-ok Override the changesets check release:dependency This PR only updates dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant