[PR #17] [MERGED] chore(deps-dev): bump prisma from 7.3.0 to 7.4.0 in /frontend #145

New issue

Closed

opened 2026-03-13 17:19:47 +03:00 by kerem · 0 comments

kerem commented

2026-03-13 17:19:47 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/adminsyspro/proxcenter-ui/pull/17
Author: @dependabot[bot]
Created: 2/19/2026
Status: ✅ Merged
Merged: 2/19/2026
Merged by: @adminsyspro

Base: main ← Head: dependabot/npm_and_yarn/frontend/prisma-7.4.0

📝 Commits (1)

afb8095 chore(deps-dev): bump prisma from 7.3.0 to 7.4.0 in /frontend

📊 Changes

3 files changed (+3077 additions, -208 deletions)

View changed files

📝 frontend/package-lock.json (+112 -49)
📝 frontend/package.json (+1 -1)
📝 frontend/pnpm-lock.yaml (+2964 -158)

📄 Description

Bumps prisma from 7.3.0 to 7.4.0.

Release notes

Sourced from prisma's releases.

7.4.0

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ORM

Caching in Prisma Client

Today’s release is a big one, as we introduce a new caching layer into Prisma ORM. But why the need for a caching layer?

In Prisma 7, the query compiler runs as a WebAssembly module directly on the JavaScript main thread. While this simplified the architecture by eliminating the separate engine process, it introduced a trade-off: every query now synchronously blocks the event loop during compilation.

For individual queries, compilation takes between 0.1ms and 1ms, which is barely noticeable in isolation. But under high concurrency this overhead adds up and creates event loop contention that affects overall application throughput.

For instance, say we have a query that is run over and over, but is a similar shape:
// These two queries have the same shape:
const alice = await prisma.user.findUnique({ where: { email: 'alice@prisma.io' } })
const bob = await prisma.user.findUnique({ where: { email: 'bob@prisma.io' } })
Prior to v7.4.0, this would be reevaluated ever time the query is run. Now, Prisma Client will extract the user-provided values and replaces them with typed placeholders, producing a normalized query shape:
prisma.user.findUnique({ where: { email: %1 } })   // cache key
                                         ↑
                              %1 = 'alice@prisma.io'  (or 'bob@prisma.io')
This normalized shape is used as a cache key. On the first call, the query is compiled as usual and the resulting plan is stored in an LRU cache. On every subsequent call with the same query shape, regardless of the actual values, the cached plan is reused instantly without invoking the compiler.

We have more details on the impact of this change and some deep dives into Prisma architecture in an upcoming blog post!

Partial Indexes (Filtered Indexes) Support

We're excited to announce Partial Indexes support in Prisma! This powerful community-contributed feature allows you to create indexes that only include rows matching specific conditions, significantly reducing index size and improving query performance.

Partial indexes are available behind the partialIndexes preview feature for PostgreSQL, SQLite, SQL Server, and CockroachDB, with full migration and introspection support.

Basic usage

Enable the preview feature in your schema:
generator client {
  provider        = "prisma-client-js"
</tr></table> 

... (truncated)

Commits

1df1c6d fix(cli-generator): outdated default generator provider (#29089)
710c25d fix: update dependencies to fix pnpm audit (#29128)
fdabc1c fix(cli): remove Prisma Pulse from CLI help message (#29093)
1677a32 docs: fix broken getting started links across repository (#28948)
See full diff 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 show <dependency name> 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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/adminsyspro/proxcenter-ui/pull/17 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 2/19/2026 **Status:** ✅ Merged **Merged:** 2/19/2026 **Merged by:** [@adminsyspro](https://github.com/adminsyspro) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/frontend/prisma-7.4.0` --- ### 📝 Commits (1) - [`afb8095`](https://github.com/adminsyspro/proxcenter-ui/commit/afb80959002f9085e5148ae3ee2ff837ce5cf2d3) chore(deps-dev): bump prisma from 7.3.0 to 7.4.0 in /frontend ### 📊 Changes **3 files changed** (+3077 additions, -208 deletions) <details> <summary>View changed files</summary> 📝 `frontend/package-lock.json` (+112 -49) 📝 `frontend/package.json` (+1 -1) 📝 `frontend/pnpm-lock.yaml` (+2964 -158) </details> ### 📄 Description Bumps [prisma](https://github.com/prisma/prisma/tree/HEAD/packages/cli) from 7.3.0 to 7.4.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>7.4.0</h2> <p>Today, we are excited to share the <code>7.4.0</code> stable release 🎉</p> <p><strong>🌟 Star this repo for notifications about new releases, bug fixes & features — or <a href="https://pris.ly/x">follow us on X</a>!</strong></p> <h1>Highlights</h1> <h2>ORM</h2> <h3>Caching in Prisma Client</h3> <p>Today’s release is a big one, as we introduce a new caching layer into Prisma ORM. But why the need for a caching layer?</p> <p>In Prisma 7, the query compiler runs as a WebAssembly module directly on the JavaScript main thread. While this simplified the architecture by eliminating the separate engine process, it introduced a trade-off: every query now synchronously blocks the event loop during compilation.</p> <p>For individual queries, compilation takes between 0.1ms and 1ms, which is barely noticeable in isolation. But under high concurrency this overhead adds up and creates event loop contention that affects overall application throughput.</p> <p>For instance, say we have a query that is run over and over, but is a similar shape:</p> <pre lang="tsx"><code>// These two queries have the same shape: const alice = await prisma.user.findUnique({ where: { email: 'alice@prisma.io' } }) const bob = await prisma.user.findUnique({ where: { email: 'bob@prisma.io' } }) </code></pre> <p>Prior to v7.4.0, this would be reevaluated ever time the query is run. Now, Prisma Client will extract the user-provided values and replaces them with typed placeholders, producing a normalized query shape:</p> <pre><code>prisma.user.findUnique({ where: { email: %1 } }) // cache key ↑ %1 = 'alice@prisma.io' (or 'bob@prisma.io') </code></pre> <p>This normalized shape is used as a cache key. On the first call, the query is compiled as usual and the resulting plan is stored in an LRU cache. On every subsequent call with the same query shape, regardless of the actual values, the cached plan is reused instantly without invoking the compiler.</p> <p>We have more details on the impact of this change and some deep dives into Prisma architecture in an upcoming blog post!</p> <h3>Partial Indexes (Filtered Indexes) Support</h3> <p>We're excited to announce <strong>Partial Indexes</strong> support in Prisma! This powerful community-contributed feature allows you to create indexes that only include rows matching specific conditions, significantly reducing index size and improving query performance.</p> <p>Partial indexes are available behind the <code>partialIndexes</code> preview feature for PostgreSQL, SQLite, SQL Server, and CockroachDB, with full migration and introspection support.</p> <p><strong>Basic usage</strong></p> <p>Enable the preview feature in your schema:</p> <pre lang="groovy"><code>generator client { provider = "prisma-client-js" </tr></table> </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/prisma/prisma/commit/1df1c6dc9477dfb2236e9231064e4df8f10c892c"><code>1df1c6d</code></a> fix(cli-generator): outdated default generator provider (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/29089">#29089</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/710c25d03903c19184d11f890fa40be366f4a7d3"><code>710c25d</code></a> fix: update dependencies to fix pnpm audit (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/29128">#29128</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/fdabc1c00f07faaa66c31f1495e94c36e181b00b"><code>fdabc1c</code></a> fix(cli): remove Prisma Pulse from CLI help message (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/29093">#29093</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/1677a32755578a85f7acaa2ae57cf11997872b41"><code>1677a32</code></a> docs: fix broken getting started links across repository (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/cli/issues/28948">#28948</a>)</li> <li>See full diff in <a href="https://github.com/prisma/prisma/commits/7.4.0/packages/cli">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=prisma&package-manager=npm_and_yarn&previous-version=7.3.0&new-version=7.4.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 show <dependency name> 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) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>