SVI/ProxmoxVE-Local
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE-Local.git synced 2026-03-31 06:23:54 -04:00
Code Issues 56 Packages Projects Releases 7 Wiki Activity

[PR #256] [MERGED] build(deps): Bump @prisma/client from 6.17.1 to 6.18.0 #292

New Issue
Open
opened 2025-11-20 04:13:58 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 04:13:58 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE-Local/pull/256
Author: @dependabot[bot]
Created: 10/27/2025
Status: ✅ Merged
Merged: 10/27/2025
Merged by: @MickLesk

Base: main ← Head: dependabot/npm_and_yarn/prisma/client-6.18.0

📝 Commits (1)

  • 5b672c9 build(deps): Bump @prisma/client from 6.17.1 to 6.18.0

📊 Changes

2 files changed (+5 additions, -5 deletions)

View changed files

📝 package-lock.json (+4 -4)
📝 package.json (+1 -1)

📄 Description

Bumps @prisma/client from 6.17.1 to 6.18.0.

Release notes

Sourced from @​prisma/client's releases.

6.18.0

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

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

Prisma ORM

Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:

  • prisma init now creates a prisma.config.ts automatically

When creating a new project with 6.18.0, prisma init will now create a prisma.config.ts file automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in the schema.prisma file are now able to be set in the prisma.config.ts, and we encourage people to migrate over to the new structure before the release of version 7, where this file will become a requirement.

  • Support for defining your datasource in prisma.config.ts

If you’re adopting the new prisma.config.ts setup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in your schema.prisma will be ignored. To set the datasource, we also must include the new engine key which we can set to "classic" , which will be required for Prisma v7

import { defineConfig, env } from "prisma/config";
export default defineConfig({
    // The Rust-compiled schema engine 
    engine: "classic",
    datasource: {
        url: env('DATABASE_URL'),
    }
});

Preparing for Prisma v7

While it has been mentioned a few times already, many of the changes in this release are here to prepare folks for the upcoming release of Prisma v7. It’s worth repeating that these changes and the migration to prisma.config.ts will be required for Prisma v7, so we’re releasing this as opt-in features for developers. But come Prisma v7, they will be the new way of configuring your project.

Prisma Postgres

Prisma Postgres is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements:

Database Metric in Console

Inside of your database console, you can now view metrics on your database usage and interactions. You can get insights into the follow:

  • Total egress
  • Average response size
  • Average query duration

In addition, you can also get insights into how to improve your query caching and gain better performance.

... (truncated)

Commits
  • 1bd7fd2 fix(tests): don't replace the process.env object (#28331)
  • 7633148 chore(deps): update engines to 6.18.0-8.34b5a692b7bd79939a9a2c3ef97d816e749cd...
  • 4078626 chore: fix jest inline snapshot update (#28330)
  • 50f6514 fix: support multiple Prisma instances with different providers (#28291)
  • 3bc04bc chore(deps): update engines to 6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39cc...
  • 6c5a217 fix(adapter-pg): historical dates (#28212)
  • 30bdd63 chore(deps): update engines to 6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7...
  • 1341489 chore(deps): update engines to 6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0...
  • c524934 chore: upgrade OpenTelemetry deps and refresh tracing setup in client (#28268)
  • 423b585 fix: revert "chore: use pnpm catalog (#28236)" (#28271)
  • Additional commits viewable in compare view

Dependabot compatibility score

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

🔄 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/community-scripts/ProxmoxVE-Local/pull/256 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 10/27/2025 **Status:** ✅ Merged **Merged:** 10/27/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/prisma/client-6.18.0` --- ### 📝 Commits (1) - [`5b672c9`](https://github.com/community-scripts/ProxmoxVE-Local/commit/5b672c9bd1864dfa1f408c01a83e333f0c559070) build(deps): Bump @prisma/client from 6.17.1 to 6.18.0 ### 📊 Changes **2 files changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+4 -4) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [@prisma/client](https://github.com/prisma/prisma/tree/HEAD/packages/client) from 6.17.1 to 6.18.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>6.18.0</h2> <p>Today, we are excited to share the <code>6.18.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> <h1>Prisma ORM</h1> <p>Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:</p> <ul> <li><code>prisma init</code> now creates a <code>prisma.config.ts</code> automatically</li> </ul> <p>When creating a new project with 6.18.0, <code>prisma init</code> will now create a <code>prisma.config.ts</code> file automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in the <code>schema.prisma</code> file are now able to be set in the <code>prisma.config.ts</code>, and we encourage people to migrate over to the new structure before the release of version 7, where this file will become a requirement.</p> <ul> <li>Support for defining your <code>datasource</code> in <code>prisma.config.ts</code></li> </ul> <p>If you’re adopting the new <code>prisma.config.ts</code> setup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in your <code>schema.prisma</code> will be ignored. To set the datasource, we also must include the new <code>engine</code> key which we can set to <code>&quot;classic&quot;</code> , which will be required for Prisma v7</p> <pre lang="tsx"><code>import { defineConfig, env } from &quot;prisma/config&quot;; export default defineConfig({ // The Rust-compiled schema engine engine: &quot;classic&quot;, datasource: { url: env('DATABASE_URL'), } }); </code></pre> <ul> <li><a href="https://redirect.github.com/prisma/prisma/pull/28291">prisma/prisma#28291</a> Support multiple Prisma instances with different providers</li> <li><a href="https://redirect.github.com/prisma/prisma/pull/28305">prisma/prisma#28305</a> Add <code>env</code> helper function</li> <li><a href="https://redirect.github.com/prisma/prisma/pull/28266">prisma/prisma#28266</a> Add support for <code>js</code> or <code>classic</code> as engine types in <code>prisma.config</code></li> <li><a href="https://redirect.github.com/prisma/prisma/pull/28139">prisma/prisma#28139</a> Map <code>Bytes</code> to <code>Uint8Array</code> depending on Typescript version</li> </ul> <h3>Preparing for Prisma v7</h3> <p>While it has been mentioned a few times already, many of the changes in this release are here to prepare folks for the upcoming release of Prisma v7. It’s worth repeating that these changes and the migration to <code>prisma.config.ts</code> will be required for Prisma v7, so we’re releasing this as opt-in features for developers. But come Prisma v7, they will be the new way of configuring your project.</p> <h1><a href="https://www.prisma.io/postgres">Prisma Postgres</a></h1> <p><a href="https://www.prisma.io/postgres">Prisma Postgres</a> is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements:</p> <h3>Database Metric in Console</h3> <p>Inside of your database console, you can now view metrics on your database usage and interactions. You can get insights into the follow:</p> <ul> <li>Total egress</li> <li>Average response size</li> <li>Average query duration</li> </ul> <p>In addition, you can also get insights into how to improve your query caching and gain better performance.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/prisma/prisma/commit/1bd7fd29d0a489591cd7d125a6f7d776412bf298"><code>1bd7fd2</code></a> fix(tests): don't replace the process.env object (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/28331">#28331</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/7633148eecce6cd43ecde303e784d382a2c92937"><code>7633148</code></a> chore(deps): update engines to 6.18.0-8.34b5a692b7bd79939a9a2c3ef97d816e749cd...</li> <li><a href="https://github.com/prisma/prisma/commit/407862680558d456b2000b9e817193461fbb2f6a"><code>4078626</code></a> chore: fix jest inline snapshot update (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/28330">#28330</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/50f651408bbf7b791ac54e79546c5afc91e8d9ec"><code>50f6514</code></a> fix: support multiple Prisma instances with different providers (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/28291">#28291</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/3bc04bc1753d905dbbef6f1a457cb7bbd18c7582"><code>3bc04bc</code></a> chore(deps): update engines to 6.18.0-7.d3fc122f88ca3ce86f67a797debfb179a39cc...</li> <li><a href="https://github.com/prisma/prisma/commit/6c5a217d60a44860ab858e0adb64570dd9a0c5bc"><code>6c5a217</code></a> fix(adapter-pg): historical dates (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/28212">#28212</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/30bdd63e3b98d96c541290bff0c61bd1a25f97f8"><code>30bdd63</code></a> chore(deps): update engines to 6.18.0-6.9bf76dbea6c9e34d59a3577015bd1e94bfda7...</li> <li><a href="https://github.com/prisma/prisma/commit/13414894c0687b899a8926854b2ded1e13c523d6"><code>1341489</code></a> chore(deps): update engines to 6.18.0-3.b03d75f1a67e62289420f5697c28a3ff8dbb0...</li> <li><a href="https://github.com/prisma/prisma/commit/c5249341dc04490c790e535062224821be4c39b0"><code>c524934</code></a> chore: upgrade OpenTelemetry deps and refresh tracing setup in client (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/28268">#28268</a>)</li> <li><a href="https://github.com/prisma/prisma/commit/423b58507879080bdc1273ca5d30b3de87e5b766"><code>423b585</code></a> fix: revert &quot;chore: use pnpm catalog (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/28236">#28236</a>)&quot; (<a href="https://github.com/prisma/prisma/tree/HEAD/packages/client/issues/28271">#28271</a>)</li> <li>Additional commits viewable in <a href="https://github.com/prisma/prisma/commits/6.18.0/packages/client">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@prisma/client&package-manager=npm_and_yarn&previous-version=6.17.1&new-version=6.18.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> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2025-11-20 04:13:58 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
feature
in progress
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE-Local#292
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?