Skip to content

Commit 69d2eba

Browse files
feat(deps): Bump @prisma/instrumentation from 6.12.0 to 6.13.0 (#17315)
Bumps [@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation) from 6.12.0 to 6.13.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.13.0</h2> <p>Today, we are excited to share the <code>6.13.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> <p>In this ORM release, we’re moving the Prisma Config file and the multi-schema feature into <a href="https://www.prisma.io/docs/orm/more/releases#generally-available-ga">General Availability</a>. This means these features now are fully production-ready and we’re looking forward to seeing what you are going to build with them!</p> <p>Additionally, support for SQL views is getting an important update to further stabilize its API.</p> <h3>Configuring Prisma via Prisma Config is now Generally Available</h3> <p>The <a href="https://www.prisma.io/docs/orm/reference/prisma-config-reference"><code>prisma.config.ts</code></a> file is Prisma ORM’s native way to provide configuration options for your project. It currently lets you specify:</p> <ul> <li>the locations for various Prisma-related assets, such as your: <ul> <li>Prisma schema file</li> <li>migrations</li> <li>SQL view definitions</li> <li>TypedSQL queries</li> </ul> </li> <li>a <code>seed</code> command to populate your database based on some executable script</li> <li>externally managed tables (see below)</li> <li>the driver adapters to be used by the Prisma CLI when interacting with your database</li> </ul> <p>Here’s an example Prisma Config file that specified custom locations for various project assets in and a seed script inside a <code>db</code> directory:</p> <pre lang="tsx"><code>import path from &quot;node:path&quot;; import { defineConfig } from &quot;prisma/config&quot;; <p>export default defineConfig({<br /> schema: path.join(&quot;db&quot;, &quot;schema.prisma&quot;),<br /> migrations: {<br /> path: path.join(&quot;db&quot;, &quot;migrations&quot;),<br /> seed: &quot;tsx db/seed.ts&quot;<br /> }<br /> });<br /> </code></pre></p> <p>Note that you’ll also see warning now if you defined a <code>prisma.seed</code> command in <code>package.json</code>.</p> <p>We’re excited to move the <a href="https://www.prisma.io/docs/orm/reference/prisma-config-reference"><code>prisma.config.ts</code></a> file into General Availability. If you used it before in your projects, you can now drop <code>earlyAccess</code> from its options:</p> <pre lang="diff"><code>import { defineConfig } from &quot;prisma/config&quot;; <p>export default defineConfig({</p> <ul> <li>earlyAccess: true,<br /> });<br /> </code></pre></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/prisma/prisma/commits/6.13.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.12.0&new-version=6.13.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>
1 parent 8e888bf commit 69d2eba

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

packages/node/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@
9494
"@opentelemetry/resources": "^2.0.0",
9595
"@opentelemetry/sdk-trace-base": "^2.0.0",
9696
"@opentelemetry/semantic-conventions": "^1.34.0",
97-
"@prisma/instrumentation": "6.12.0",
97+
"@prisma/instrumentation": "6.13.0",
9898
"@sentry/core": "10.1.0",
9999
"@sentry/node-core": "10.1.0",
100100
"@sentry/opentelemetry": "10.1.0",

yarn.lock

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6305,10 +6305,10 @@
63056305
resolved "https://registry.yarnpkg.com/@poppinss/exception/-/exception-1.2.2.tgz#8d30d42e126c54fe84e997433e4dcac610090743"
63066306
integrity sha512-m7bpKCD4QMlFCjA/nKTs23fuvoVFoA83brRKmObCUNmi/9tVu8Ve3w4YQAnJu4q3Tjf5fr685HYIC/IA2zHRSg==
63076307

6308-
"@prisma/instrumentation@6.12.0":
6309-
version "6.12.0"
6310-
resolved "https://registry.yarnpkg.com/@prisma/instrumentation/-/instrumentation-6.12.0.tgz#fd47ed75bfb8f1180a0d77695084f2c0c46bb4d7"
6311-
integrity sha512-UfwLME9uRDKGOu06Yrj5ERT5XVx4xvdyPsjRtQl2gY2ZgSK6c2ZNsKfEPVQHwrNl4hu2m9Rw1KCcy0sdEnefKw==
6308+
"@prisma/instrumentation@6.13.0":
6309+
version "6.13.0"
6310+
resolved "https://registry.yarnpkg.com/@prisma/instrumentation/-/instrumentation-6.13.0.tgz#f2f774162b9247c870f306828da580c5102ff679"
6311+
integrity sha512-b97b0sBycGh89RQcqobSgjGl3jwPaC5cQIOFod6EX1v0zIxlXPmL3ckSXxoHpy+Js0QV/tgCzFvqicMJCtezBA==
63126312
dependencies:
63136313
"@opentelemetry/instrumentation" "^0.52.0 || ^0.53.0 || ^0.54.0 || ^0.55.0 || ^0.56.0 || ^0.57.0"
63146314

0 commit comments

Comments
 (0)