feat(deps): bump @prisma/instrumentation from 6.13.0 to 6.14.0 (#17466)

Bumps
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 6.13.0 to 6.14.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/prisma/prisma/releases"><code>@​prisma/instrumentation</code>'s
releases</a>.</em></p>
<blockquote>
<h2>6.14.0</h2>
<p>Today, we are excited to share the <code>6.14.0</code> stable
release 🎉</p>
<p><strong>🌟 Star this repo for notifications about new releases, bug
fixes &amp; features — or <a href="https://pris.ly/x">follow us on
X</a>!</strong></p>
<h2>Highlights</h2>
<h3><code>@unique</code> attributes for SQL views (Preview)</h3>
<p><a href="https://pris.ly/release/6.13.0">Last release</a>, we
improved the robustness of <a
href="https://www.prisma.io/docs/orm/prisma-schema/data-model/views">SQL
views</a> defined in the Prisma schema. Views are <em>virtual</em>
tables that don't allows for defining unique constraints, indexes or
foreign keys in the underlying database.</p>
<p>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 <code>@unique</code> attribute for views. This
attribute enables:</p>
<ul>
<li>relationships involving views</li>
<li><code>findUnique</code> queries, cursor-based pagination &amp;
implicit ordering for views</li>
</ul>
<p>Here's an example schema using <code>@unique</code> and defining a
relationship from a model to a view:</p>
<pre lang="prisma"><code>model User {
  id        Int            @id @default(autoincrement())
  email     String         @unique
  posts     Post[]
stats UserPostStats? @relation(fields: [email], references: [userEmail])
}
<p>model Post {
id Int <a href="https://github.com/id"><code>@​id</code></a> <a
href="https://github.com/default"><code>@​default</code></a>(autoincrement())
title     String
published Boolean <a
href="https://github.com/default"><code>@​default</code></a>(false)
createdAt DateTime <a
href="https://github.com/default"><code>@​default</code></a>(now())
authorId  Int?
author User? <a
href="https://github.com/relation"><code>@​relation</code></a>(fields:
[authorId], references: [id])
}</p>
<p>view UserPostStats {
userEmail String <a
href="https://github.com/unique"><code>@​unique</code></a>
totalPosts       BigInt?
publishedPosts   BigInt?
unpublishedPosts BigInt?
latestPostDate DateTime? <a
href="https://github.com/db"><code>@​db</code></a>.Timestamp(6)
user             User?
}
</code></pre></p>
<!-- raw HTML omitted -->
<pre lang="sql"><code>CREATE OR REPLACE VIEW &quot;UserPostStats&quot;
AS
SELECT 
&lt;/tr&gt;&lt;/table&gt; 
</code></pre>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/prisma/prisma/commit/dd823f6b26e1b84bb909e115024eb762bf430e53"><code>dd823f6</code></a>
feat(client): drop deprecated middleware feature (<a
href="https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation/issues/27799">#27799</a>)</li>
<li>See full diff in <a
href="https://github.com/prisma/prisma/commits/6.14.0/packages/instrumentation">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@prisma/instrumentation&package-manager=npm_and_yarn&previous-version=6.13.0&new-version=6.14.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 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 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>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

packages/node/package.json

@@ -94,7 +94,7 @@
     "@opentelemetry/resources": "^2.0.0",
     "@opentelemetry/sdk-trace-base": "^2.0.0",
     "@opentelemetry/semantic-conventions": "^1.34.0",
-    "@prisma/instrumentation": "6.13.0",
+    "@prisma/instrumentation": "6.14.0",
     "@sentry/core": "10.5.0",
     "@sentry/node-core": "10.5.0",
     "@sentry/opentelemetry": "10.5.0",

yarn.lock

@@ -6296,10 +6296,10 @@
   resolved "https://registry.yarnpkg.com/@poppinss/exception/-/exception-1.2.2.tgz#8d30d42e126c54fe84e997433e4dcac610090743"
   integrity sha512-m7bpKCD4QMlFCjA/nKTs23fuvoVFoA83brRKmObCUNmi/9tVu8Ve3w4YQAnJu4q3Tjf5fr685HYIC/IA2zHRSg==
 
-"@prisma/instrumentation@6.13.0":
-  version "6.13.0"
-  resolved "https://registry.yarnpkg.com/@prisma/instrumentation/-/instrumentation-6.13.0.tgz#f2f774162b9247c870f306828da580c5102ff679"
-  integrity sha512-b97b0sBycGh89RQcqobSgjGl3jwPaC5cQIOFod6EX1v0zIxlXPmL3ckSXxoHpy+Js0QV/tgCzFvqicMJCtezBA==
+"@prisma/instrumentation@6.14.0":
+  version "6.14.0"
+  resolved "https://registry.yarnpkg.com/@prisma/instrumentation/-/instrumentation-6.14.0.tgz#8f6e43b73ee2b88b98cec901457f4da7da13aea3"
+  integrity sha512-Po/Hry5bAeunRDq0yAQueKookW3glpP+qjjvvyOfm6dI2KG5/Y6Bgg3ahyWd7B0u2E+Wf9xRk2rtdda7ySgK1A==
   dependencies:
     "@opentelemetry/instrumentation" "^0.52.0 || ^0.53.0 || ^0.54.0 || ^0.55.0 || ^0.56.0 || ^0.57.0"