Bump the prisma group with 2 updates

[dependabot]

Updates the requirements on @prisma/client and prisma to permit the latest version.
Updates @prisma/client to 6.14.0

Release notes

Sourced from @​prisma/client's releases.

6.14.0

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

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

Highlights

@unique attributes for SQL views (Preview)

Last release, we improved the robustness of SQL views defined in the Prisma schema. Views are virtual tables that don't allows for defining unique constraints, indexes or foreign keys in the underlying database.

However, as an application developer, it can be convenient to also define relationships involving views or paginate them using cursors. We've received this feedback from several people who had been using views in that way with Prisma ORM, so in this release we're re-introducing the @unique attribute for views. This attribute enables:

• relationships involving views
• findUnique queries, cursor-based pagination & implicit ordering for views

Here's an example schema using @unique and defining a relationship from a model to a view:

model User {
  id        Int            @id @default(autoincrement())
  email     String         @unique
  posts     Post[]
  stats     UserPostStats? @relation(fields: [email], references: [userEmail])
}
model Post {
id        Int      @​id @​default(autoincrement())
title     String
published Boolean  @​default(false)
createdAt DateTime @​default(now())
authorId  Int?
author    User?    @​relation(fields: [authorId], references: [id])
}
view UserPostStats {
userEmail        String    @​unique
totalPosts       BigInt?
publishedPosts   BigInt?
unpublishedPosts BigInt?
latestPostDate   DateTime? @​db.Timestamp(6)
user             User?
}

CREATE OR REPLACE VIEW "UserPostStats" AS
SELECT 
</tr></table> 

... (truncated)

Commits

• f1f2669 chore(deps): update engines to 6.14.0-25.717184b7b35ea05dfa71a3236b7af656013e...
• 71f115e chore: revert #27887 (#27889)
• 86b72d8 chore(deps): update engines to 6.14.0-24.944e9a8aab0cc8395d8eb5912777c1e5bebf...
• 9b0899d chore: don't build wasm-base64 cjs bundles (#27887)
• 21765b0 fix: ORM-850 improve client options type performance (#27777)
• f92c421 refactor(client): extract reusable parts of batch request handling (#27879)
• d9c590b chore(deps): update engines to 6.14.0-22.0b03dd192b3c1459e1142ba36decb4194ca1...
• 8420681 chore(deps): update engines to 6.14.0-20.21db42295e1eec1ae16580cd07cc0aefd0f2...
• 7dddc22 fix(qc): align tx manager errors (#27861)
• 07cc0bc chore(deps): update engines to 6.14.0-18.fbfd9bd6424bc01bfbd02a26ef00c2b14d01...
• Additional commits viewable in compare view

Updates prisma to 6.14.0

Release notes

Sourced from prisma's releases.

6.14.0

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

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

Highlights

@unique attributes for SQL views (Preview)

Last release, we improved the robustness of SQL views defined in the Prisma schema. Views are virtual tables that don't allows for defining unique constraints, indexes or foreign keys in the underlying database.

However, as an application developer, it can be convenient to also define relationships involving views or paginate them using cursors. We've received this feedback from several people who had been using views in that way with Prisma ORM, so in this release we're re-introducing the @unique attribute for views. This attribute enables:

• relationships involving views
• findUnique queries, cursor-based pagination & implicit ordering for views

Here's an example schema using @unique and defining a relationship from a model to a view:

model User {
  id        Int            @id @default(autoincrement())
  email     String         @unique
  posts     Post[]
  stats     UserPostStats? @relation(fields: [email], references: [userEmail])
}
model Post {
id        Int      @​id @​default(autoincrement())
title     String
published Boolean  @​default(false)
createdAt DateTime @​default(now())
authorId  Int?
author    User?    @​relation(fields: [authorId], references: [id])
}
view UserPostStats {
userEmail        String    @​unique
totalPosts       BigInt?
publishedPosts   BigInt?
unpublishedPosts BigInt?
latestPostDate   DateTime? @​db.Timestamp(6)
user             User?
}

CREATE OR REPLACE VIEW "UserPostStats" AS
SELECT 
</tr></table> 

... (truncated)

Commits

• 21765b0 fix: ORM-850 improve client options type performance (#27777)
• 114dd96 fix(client): prisma-client generator with moduleFormat = "cjs" (#27828)
• 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 will merge this PR once CI passes on it, as requested by @samchon.

---

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 <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

[samchon]

@dependabot merge