Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: Bump the prisma group with 2 updates (#2190)
Bumps the prisma group with 2 updates: [@prisma/client](https://github.com/prisma/prisma/tree/HEAD/packages/client) and [prisma](https://github.com/prisma/prisma/tree/HEAD/packages/cli). Updates `@prisma/client` from 4.16.2 to 5.2.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/prisma/prisma/releases"><code>@prisma/client</code>'s releases</a>.</em></p> <blockquote> <h2>5.2.0</h2> <p>🌟 <strong>Help us spread the word about Prisma by starring the repo or <a href="https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v5.2.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.2.0">tweeting</a> about the release.</strong> 🌟</p> <h1>Highlights</h1> <h2>Improved Prisma Client experience for Prisma Accelerate and Data Proxy</h2> <p>In this release, we’ve made the following improvements to Prisma Client when using <a href="https://www.prisma.io/data-platform/accelerate">Prisma Accelerate</a> or <a href="https://www.prisma.io/data-platform/proxy">Prisma Data Proxy</a>:</p> <ul> <li> <p>Prisma Client will now automatically determine how it should connect to the database depending on the protocol in the connection string. If the connection string starts with <code>prisma://</code>, Prisma Client will try to connect to your database using Prisma Accelerate or Prisma Data Proxy.</p> </li> <li> <p>Prisma Studio now works with Prisma Data Proxy and Prisma Accelerate.</p> </li> <li> <p>We’ve introduced a new <code>--no-engine</code> flag which will prevent a Query Engine file from being included in the generated Prisma Client. This flag will also help ensure the bundle size of your application remains small by excluding the Query Engine files from the generated Prisma Client.</p> <pre lang="bash"><code>prisma generate --no-engine </code></pre> <p>The <code>--data-proxy</code> and <code>--accelerate</code> flags have not been removed but are now aliases for the new <code>--no-engine</code> flag.</p> <p>We recommend using the <code>--no-engine</code> flag when generating Prisma Client that uses either Accelerate or Data Proxy.</p> </li> </ul> <h2>Simplified connection string override in Prisma Client</h2> <p>This release simplifies the API used when programmatically overriding the connection string by introducing the <code>datasourceUrl</code> property in Prisma Client’s constructor. This means you do not have to use the datasource name defined in your Prisma schema.</p> <pre lang="tsx"><code>const prisma = new PrismaClient({ datasourceUrl: "postgresql://johndoe:randompassword@localhost:5432/mydb", }) </code></pre> <h2>Query performance improvements</h2> <p>Continuing our work from <a href="https://github.com/prisma/prisma/releases/tag/5.1.0">5.1.0</a> we made further performance improvements around the queries Prisma executes, targeting <a href="https://www.prisma.io/docs/concepts/components/prisma-schema/relations/one-to-one-relations">one-to-many relation fields</a> and <a href="https://www.prisma.io/docs/concepts/components/prisma-client/relation-queries#update-all-related-records-or-filter">nested updates</a>.</p> <h3>Use <code>LIMIT</code> in one-to-many relations on a single parent</h3> <p>In cases where there is a single parent with a one-to-many relation included (<code>findFirst</code>, <code>findUnique</code>, <code>findMany({ take: 1 })</code>), we now utilize <code>LIMIT</code> at the database level to restrict the number of related items returned instead of retrieving all related items into memory and performing a <code>take</code> in memory.</p> <p>For situations where you have many related objects but only need a few, you should see a dramatic improvement in speed and memory usage.</p> <p><strong>Note</strong>: we are still working on bringing this improvement to other parts of Prisma Client in upcoming releases. If multiple parent records are returned, the previous behavior is used.</p> <h3>Further improvements for nested writes</h3> <p>Thanks to our introduction of using <code>RETURNING</code> in some cases in 5.1.0, we could now improve performance in nested writes by removing reload nodes. This will now result in one less query per relation traversed in a nested write. For more info, <a href="https://redirect.github.com/prisma/prisma-engines/pull/4108">check out the pull request</a>.</p> <h4>Prisma Client query</h4> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/prisma/prisma/commit/25258e0456fd83ad0dd4169b87ef98e0ebcfb001"><code>25258e0</code></a> chore(deps): update engines to 5.3.0-1.98bd6d18365f86d632686c26d1b26d8e054c67...</li> <li><a href="https://github.com/prisma/prisma/commit/509014ba7a760079614ffc51e609f97ef3ce9195"><code>509014b</code></a> fix(client): error for missing env on cloudflare (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/20782">#20782</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/a7e4353f366953b41fecc0a79fafc3c2cdee400f"><code>a7e4353</code></a> test(cli): studio via mini-proxy (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/20781">#20781</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/e3ecd917a8dc6aa623564dd13c65563357f15ab3"><code>e3ecd91</code></a> fix(client): use Proxy for "browser" import (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/20683">#20683</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/02164a6cefd7780f252c3665ef2090f9a8b5f8cb"><code>02164a6</code></a> chore(deps): update engines to 5.2.0-25.2804dc98259d2ea960602aca6b8e7fdc03c17...</li> <li><a href="https://github.com/prisma/prisma/commit/0e7a144117926305e93e611bcaf18ecc3491e544"><code>0e7a144</code></a> fix(client): improve edge env var errors (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/20734">#20734</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/01d6118ab097e0a259f2543fcf214b84e2ad76ee"><code>01d6118</code></a> fix(client): Add missing aliases for legacy args names (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/20726">#20726</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/41e09d4475b89cd0c580750a20a91f21f0d64fab"><code>41e09d4</code></a> feat(client): Add shortuct for overriding single datasource URL (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/20740">#20740</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/9ff064e24c75e04c4130c359f42910fc580aed81"><code>9ff064e</code></a> chore(deps): update engines to 5.2.0-24.0bc8ee687eb17771fa7ca5167bcad38f8f2d0...</li> <li><a href="https://github.com/prisma/prisma/commit/e77d823c72af02d2a0aff7e43204b0f6dabedea7"><code>e77d823</code></a> fix(client): error when accelerate is used with metrics (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/20732">#20732</a>)</li> <li>Additional commits viewable in <a href="https://github.com/prisma/prisma/commits/5.2.0/packages/client">compare view</a></li> </ul> </details> <br /> Updates `prisma` from 4.16.2 to 5.2.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/prisma/prisma/releases">prisma's releases</a>.</em></p> <blockquote> <h2>5.2.0</h2> <p>🌟 <strong>Help us spread the word about Prisma by starring the repo or <a href="https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v5.2.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.2.0">tweeting</a> about the release.</strong> 🌟</p> <h1>Highlights</h1> <h2>Improved Prisma Client experience for Prisma Accelerate and Data Proxy</h2> <p>In this release, we’ve made the following improvements to Prisma Client when using <a href="https://www.prisma.io/data-platform/accelerate">Prisma Accelerate</a> or <a href="https://www.prisma.io/data-platform/proxy">Prisma Data Proxy</a>:</p> <ul> <li> <p>Prisma Client will now automatically determine how it should connect to the database depending on the protocol in the connection string. If the connection string starts with <code>prisma://</code>, Prisma Client will try to connect to your database using Prisma Accelerate or Prisma Data Proxy.</p> </li> <li> <p>Prisma Studio now works with Prisma Data Proxy and Prisma Accelerate.</p> </li> <li> <p>We’ve introduced a new <code>--no-engine</code> flag which will prevent a Query Engine file from being included in the generated Prisma Client. This flag will also help ensure the bundle size of your application remains small by excluding the Query Engine files from the generated Prisma Client.</p> <pre lang="bash"><code>prisma generate --no-engine </code></pre> <p>The <code>--data-proxy</code> and <code>--accelerate</code> flags have not been removed but are now aliases for the new <code>--no-engine</code> flag.</p> <p>We recommend using the <code>--no-engine</code> flag when generating Prisma Client that uses either Accelerate or Data Proxy.</p> </li> </ul> <h2>Simplified connection string override in Prisma Client</h2> <p>This release simplifies the API used when programmatically overriding the connection string by introducing the <code>datasourceUrl</code> property in Prisma Client’s constructor. This means you do not have to use the datasource name defined in your Prisma schema.</p> <pre lang="tsx"><code>const prisma = new PrismaClient({ datasourceUrl: "postgresql://johndoe:randompassword@localhost:5432/mydb", }) </code></pre> <h2>Query performance improvements</h2> <p>Continuing our work from <a href="https://github.com/prisma/prisma/releases/tag/5.1.0">5.1.0</a> we made further performance improvements around the queries Prisma executes, targeting <a href="https://www.prisma.io/docs/concepts/components/prisma-schema/relations/one-to-one-relations">one-to-many relation fields</a> and <a href="https://www.prisma.io/docs/concepts/components/prisma-client/relation-queries#update-all-related-records-or-filter">nested updates</a>.</p> <h3>Use <code>LIMIT</code> in one-to-many relations on a single parent</h3> <p>In cases where there is a single parent with a one-to-many relation included (<code>findFirst</code>, <code>findUnique</code>, <code>findMany({ take: 1 })</code>), we now utilize <code>LIMIT</code> at the database level to restrict the number of related items returned instead of retrieving all related items into memory and performing a <code>take</code> in memory.</p> <p>For situations where you have many related objects but only need a few, you should see a dramatic improvement in speed and memory usage.</p> <p><strong>Note</strong>: we are still working on bringing this improvement to other parts of Prisma Client in upcoming releases. If multiple parent records are returned, the previous behavior is used.</p> <h3>Further improvements for nested writes</h3> <p>Thanks to our introduction of using <code>RETURNING</code> in some cases in 5.1.0, we could now improve performance in nested writes by removing reload nodes. This will now result in one less query per relation traversed in a nested write. For more info, <a href="https://redirect.github.com/prisma/prisma-engines/pull/4108">check out the pull request</a>.</p> <h4>Prisma Client query</h4> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/prisma/prisma/commit/a7e4353f366953b41fecc0a79fafc3c2cdee400f"><code>a7e4353</code></a> test(cli): studio via mini-proxy (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20781">#20781</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/f5eac803018d5a15f80eee0fc66fdaeb467826d2"><code>f5eac80</code></a> fix(cli): incorrect url hardcoding warning (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20753">#20753</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/b3a29b801add0eea7f204bcfaed54f8689beef8d"><code>b3a29b8</code></a> refactor(cli): improve generation hints (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20731">#20731</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/21a7d9bb9e4bbe5a307720d3c85e7793e7064807"><code>21a7d9b</code></a> fix(client): remove data proxy links and mentions (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20716">#20716</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/673089454fa433c9947a4945495655c1ae8dcbf4"><code>6730894</code></a> feat(client, cli): <code>--no-engine</code> (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20692">#20692</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/fdaa9845eaafd12f8c500a65a17e44af9a3e27ee"><code>fdaa984</code></a> feat(client, cli): dynamic prisma:// urls engine loading (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20594">#20594</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/d2df0d19b1074d50e498c105eca52f1feef54e52"><code>d2df0d1</code></a> chore(deps): update esbuild packages (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/17695">#17695</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/a4831af2a91cb5b90d7319f1f1ef84f007b90f2e"><code>a4831af</code></a> chore(deps): update dependency <code>@swc/jest</code> to v0.2.29 (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20705">#20705</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/e4d6595a94dfea26d017d37f071b6a6d5cdac195"><code>e4d6595</code></a> chore: upgrade esbuild (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20671">#20671</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/cce287267428239d748c969bee727200b0d171d9"><code>cce2872</code></a> chore(deps): update studio to v0.494.0 (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/20688">#20688</a>)</li> <li>Additional commits viewable in <a href="https://github.com/prisma/prisma/commits/5.2.0/packages/cli">compare view</a></li> </ul> </details> <br /> 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information