fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@commitlint/cli (source)	^19.5.0 -> ^19.8.0					devDependencies	minor
@commitlint/config-conventional (source)	^19.5.0 -> ^19.8.0					devDependencies	minor
@discordjs/builders (source)	^1.9.0 -> ^1.10.1					dependencies	patch
@prisma/client (source)	^6.0.0 -> ^6.6.0					dependencies	minor
@sapphire/iterator-utilities (source)	^2.0.0 -> ^2.0.1					dependencies	patch
@sapphire/result (source)	^2.6.6 -> ^2.7.2					dependencies	patch
@sapphire/time-utilities (source)	^1.7.12 -> ^1.7.14					dependencies	patch
@sapphire/utilities (source)	^3.17.0 -> ^3.18.2					dependencies	patch
@skyra/http-framework (source)	^2.1.0 -> ^2.2.0					dependencies	patch
@types/node (source)	^22.8.6 -> ^22.14.0					devDependencies	minor
docker/build-push-action	v6.9.0 -> v6.15.0					action	minor
docker/login-action	v3.3.0 -> v3.4.0					action	minor
docker/setup-buildx-action	v3.7.1 -> v3.10.0					action	minor
eslint-config-prettier	^10.0.1 -> ^10.1.1					devDependencies	minor
eslint-plugin-prettier	^5.2.1 -> ^5.2.6					devDependencies	patch
lint-staged	^15.2.10 -> ^15.5.0					devDependencies	minor
node (source)	22.11.0 -> 22.14.0					volta	minor
prettier (source)	^3.3.3 -> ^3.5.3					devDependencies	minor
prisma (source)	^6.0.0 -> ^6.6.0					devDependencies	minor
tslib (source)	^2.8.0 -> ^2.8.1					dependencies	patch
yarn (source)	4.5.1 -> 4.8.1					packageManager	minor

---

Release Notes

conventional-changelog/commitlint (@​commitlint/cli)

v19.8.0

Compare Source

Performance Improvements

• use node: prefix to bypass require.cache call for builtins (#​4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package @​commitlint/cli

19.6.1 (2024-12-15)

Note: Version bump only for package @​commitlint/cli

v19.7.1

Compare Source

Note: Version bump only for package @​commitlint/cli

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.8.0

Compare Source

Performance Improvements

• use node: prefix to bypass require.cache call for builtins (#​4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package @​commitlint/config-conventional

v19.7.1

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

discordjs/discord.js (@​discordjs/builders)

v1.10.1

Compare Source

Bug Fixes

• EmbedBuilder: Allow empty name and value on fields (#​10747) (49ef3a8)

prisma/prisma (@​prisma/client)

v6.6.0

Compare Source

Today, we are excited to share the 6.6.0 stable release 🎉 This version comes packed with exciting features, we can't wait to see what you're going to build with it!

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

ESM support with more flexible prisma-client generator (Early Access)

We are excited to introduce a new prisma-client generator that's more flexible, comes with ESM support and removes any magic behaviours that may cause friction with the current prisma-client-js generator.

Note: The prisma-client generator is currently in Early Access and will likely have some breaking changes in the next releases.

Here are the main differences:

• Requires an output path; no “magic” generation into node_modules any more
• Supports ESM and CommonJS via the moduleFormat field
• Outputs plain TypeScript that's bundled just like the rest of your application code

Here's how you can use the new prisma-client generator in your Prisma schema:

// prisma/schema.prisma
generator client {
  provider     = "prisma-client"           // no `-js` at the end
  output       = "../src/generated/prisma" // `output` is required
  moduleFormat = "esm"                     // or `"cjs"` for CommonJS
}

In your application, you can then import the PrismaClient constructor (and anything else) from the generated folder:

// src/index.ts
import { PrismaClient } from './generated/prisma/client'

⚠️ Important: We recommend that you add the output path to .gitignore so that the query engine that's part of the generated Prisma Client is kept out of version control:

##### .gitignore
./src/generated/prisma

📚 Learn more in the docs.

Cloudflare D1 & Turso/LibSQL migrations (Early Access)

Cloudflare D1 and Turso are popular database providers that are both based on SQLite. While you can query them using the respective driver adapter for D1 or Turso, previous versions of Prisma ORM weren't able to make schema changes against these databases.

With today's release, we're sharing the first Early Access version of native D1 migration support for the following commands:

• prisma db push: Updates the schema of the remote database based on your Prisma schema
• prisma db pull: Introspects the schema of the remote database and updates your local Prisma schema
• prisma migrate diff: Outputs the difference between the schema of the remote database and your local Prisma schema

Note: Support for prisma migrate dev and prisma migrate deploy will come very soon!

To use these commands, you need to connect the Prisma CLI to your D1 or Turso instance by using the driver adapter in your prisma.config.ts file. Here is an example for D1:

import path from 'node:path'
import type { PrismaConfig } from 'prisma'
import { PrismaD1HTTP } from '@​prisma/adapter-d1'

// import your .env file
import 'dotenv/config'

type Env = {
  CLOUDFLARE_D1_TOKEN: string
  CLOUDFLARE_ACCOUNT_ID: string
  CLOUDFLARE_DATABASE_ID: string
}

export default {
  earlyAccess: true,
  schema: path.join('prisma', 'schema.prisma'),

  migrate: {
    async adapter(env) {
      return new PrismaD1HTTP({
        CLOUDFLARE_D1_TOKEN: env.CLOUDFLARE_D1_TOKEN,
        CLOUDFLARE_ACCOUNT_ID: env.CLOUDFLARE_ACCOUNT_ID,
        CLOUDFLARE_DATABASE_ID: env.CLOUDFLARE_DATABASE_ID,
      })
    },
  },
} satisfies PrismaConfig<Env>

With that setup, you can now execute schema changes against your D1 instance by running:

npx prisma db push

📚 Learn more in the docs:

• Cloudflare D1
• Turso / LibSQL

MCP server to manage Prisma Postgres via LLMs (Preview)

Prisma Postgres is the first serverless database without cold starts. Designed for optimal efficiency and high performance, it's the perfect database to be used alongside AI tools like Cursor, Windsurf, Lovable or co.dev. In this ORM release, we're adding a command to start a Prisma MCP server that you can integrate in your AI development environment. Thanks to that MCP server, you can now:

• tell your AI agent to create new DB instances
• design your data model
• chat through a database migration

… and much more.

To get started, add this snippet to the MCP configuration of your favorite AI tool and get started:

{
  "mcpServers": {
    "Prisma": {
      "command": "npx",
      "args": ["-y", "prisma", "mcp"]
    }
  }
}

📚 Learn more in the docs.

New --prompt option on prisma init

You can now pass a --prompt option to the prisma init command to have it scaffold a Prisma schema for you and deploy it to a fresh Prisma Postgres instance:

npx prisma init --prompt "Simple habit tracker application"

For everyone, following social media trends, we also created an alias called --vibe for you 😉

npx prisma init --vibe "Cat meme generator"

Improved API for using driver adapters

In this release, we are introducing a nice DX improvement for driver adapters. Driver adapters let you access your database using JS-native drivers with Prisma ORM.

Before 6.6.0

Earlier versions of Prisma ORM required you to first instantiate the driver itself, and then use that instance to create the Prisma driver adapter. Here is an example using the @libsql/client driver for LibSQL:

import { createClient } from '@​libsql/client'
import { PrismaLibSQL } from '@​prisma/adapter-libsql'
import { PrismaClient } from '@​prisma/client'

// Old way of using driver adapters (before 6.6.0)
const driver = createClient({
  url: env.LIBSQL_DATABASE_URL,
  authToken: env.LIBSQL_DATABASE_TOKEN,
})
const adapter = new PrismaLibSQL(driver)

const prisma = new PrismaClient({ adapter })

6.6.0 and later

As of this release, you instantiate the driver adapter directly with the options of your preferred JS-native driver.:

import { PrismaLibSQL } from '@​prisma/adapter-libsql'
import { PrismaClient } from '../prisma/prisma-client'

const adapter = new PrismaLibSQL({
  url: env.LIBSQL_DATABASE_URL,
  authToken: env.LIBSQL_DATABASE_TOKEN,
})

const prisma = new PrismaClient({ adapter })

No more Bun issues if Node.js is not installed

Bun users reported an issue that prisma generate would hang if Node.js installed on their machine. This is now fixed and Bun users can generate Prisma Client without issues.

Company news

Enterprise support

Prisma offers an enterprise support plan for Prisma ORM. Get direct help from our team and a joint slack channel! With Prisma ORM 7 on the horizon, this is a great time to upgrade your support today.

We are hiring: Developer Support Engineer

If you care about making developers successful, join us as a Developer Support Engineer.

v6.5.0

Compare Source

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟

Highlights

Databases can only be reset manually and explicitly

In previous versions, if Prisma ORM determined that a migrate command could not be applied cleanly to the underlying database, you would get a message like this one:

? We need to reset the "public" schema at "db.url.com:5432"
Do you want to continue? All data will be lost. (y/N)

While "no" was the default, we've determined that having this prompt in the first place was a mistake. In this version we're removing the prompt entirely and instead exiting with an appropriate error message.

To get the previous behavior, you will need to run prisma migrate reset directly.

Support for prisma.config.ts in Prisma Studio

We've expanded support for our prisma.config.ts file to include Prisma Studio!

To use the new config file, including the ability to connect to driver adapter enabled databases with Prisma Studio, add a studio block to your prisma.config.ts file:

import path from 'node:path'
import type { PrismaConfig } from 'prisma'
import { PrismaLibSQL } from '@​prisma/adapter-libsql'
import { createClient } from '@​libsql/client'

export default {
  earlyAccess: true,
  schema: {
    kind: 'single',
    filePath: './prisma/schema.prisma',
  },
  studio: {
    adapter: async (env: unknown) => {
      const connectionString = `file:./dev.db'
      const libsql = createClient({
        url: connectionString,
      })
      return new PrismaLibSQL(libsql)
    },
  },
} satisfies PrismaConfig

Notice how this looks a little different from last release! Instead of an @prisma/config package there’s now two different options:

1. Using the defineConfig helper exported by prisma/config.
2. Using the PrismaConfig utility type exported by Prisma.

All the relevant info for the prisma.config.ts file, including these new ways of defining your config, can be found in our docs.

Allow for chaining $on and $extends.

In previous versions of Prisma ORM, the return type of the $on client method was void. This did not allow for chaining $on() and $extends() calls, as $on is not available on extended clients.

In this version we've resolved this issue and $on will now return the modified Prisma Client.

Community fixes

We have a number of community-submitted fixes that improve Prisma ORM:

• Allow for binaries to be loaded from local network. Thank you @​RaHehl!
• Enhance type safety of the AtLeast utility type. Thank you @​de-novo!
• Resolve a race condition in the NextJS monorepo plugin. Thank you @​toniopelo!
• allow for filtering out spans with PrismaInstrumentation. Thank you @​overbit!

Prisma is hiring

Join us at Prisma and work on our TypeScript ORM (now faster than ever) and our Cloud products like Prisma Postgres (now in GA!)

We currently have two open roles in our Engineering team:

• Developer Support Engineer (Americas)
• Senior Engineering Manager

If these don’t fit, you can still check out our jobs page and send a general application.

Enterprise support

Prisma offers an enterprise support plan for Prisma ORM. Get direct help from our team and a joint slack channel! With Prisma ORM 7 on the horizon this is a great time to upgrade your support today.

Credits

Thank you to @​overbit, @​RaHehl, @​toniopelo, and @​de-novo for your contributions to this release!

v6.4.1

Compare Source

Today, we are issuing the 6.4.1 patch release. It fixes a few issues with the NPS survey and makes it respect the --no-hints CLI flag.

Fixes

Prisma CLI

• https://github.com/prisma/prisma/issues/26364

v6.4.0

Compare Source

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟

Highlights

TypeScript-based configuration with prisma.config.ts (Early Access)

In this release, we're introducing an Early Access version of a TypeScript-based configuration file for Prisma ORM: prisma.config.ts.

This file will serve as a central configuration point for Prisma ORM:

import path from 'node:path'

export default {
  earlyAccess: true, // required while in Early Access

  schema: {
    kind: 'single', // use 'multi' if you're using the `prismaSchemaFolder` preview feature
    filePath: path.join('custom', 'prisma', 'schema.prisma')
  }
  
})

With this file you are able to run any arbitrary code needed to get values required by Prisma ORM, such as database URLs from a secret store or fine-grained control of settings. It needs to live in the current working directory from where you're executing Prisma CLI commands (typically, the root of your project).

Note: If you're using prisma.config.ts, the Prisma CLI will not load environment variables from .env files. If you want to use a .env file with prisma.config.ts, you'll need to load the environment variables manually using the dotenv package (see here).

Learn more about the new prisma.config.ts file in the docs.

Case-insensitive mode in JSON filters

You can now do case-insensitive filtering on JSON data.

Just use the new mode option when filtering using string_contains, string_starts_with or string_ends_with in a JSON object and set it to "insensitive":

await prisma.user.findMany({
  where: {
    pets: {
      path: ['favorites', 'catBreed'],
      string_contains: 'Van',
      mode: "insensitive",
    },
  },
});

The above query returns all users where the favorites.catBreed value contains "Van" or "van".

Thanks to @​lubosmato who implemented this feature 🎉

Improved CockroachDB migration speed

In this release we found some inefficiencies in our migration engine that was impacting CockroachDB migrations. In 6.4.0, CockroachDB migrations should be significantly faster.

Calling all devs: Give us your feedback!

Prisma ORM's community keeps us going. To make sure that we're focused on what the community needs, we would like to get your feedback via our online feedback form.

Credits

Huge thanks to @​lubosmato, @​notomo, @​Mayureshd-18, @​mydea, @​omar-dulaimi and @​Hazmi35 for helping out with this release!

v6.3.1

Compare Source

This patch releases introduces improvements to the prisma init output when invoked to with the --db option.

Run npx prisma@latest init --db to get an instant Prisma Postgres database.

v6.3.0

Compare Source

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟

Highlights

A brand new Prisma Studio

In this release we've included several great improvements to Prisma Studio's developer experience. You can learn all about the changes we've made in our release blog post, but here's a short list:

Prisma Studio is back in the Console

Fans of Prisma Data Browser rejoice! The new Prisma Studio is now in the Prisma Console and is available for all PostgreSQL and MySQL databases.

A new model viewer

Previously, switching from model to model in Prisma Studio would require backing all the way out to the model view, then digging in again. With our new UI, it's easy to switch from model to model while keeping your place.

A new editing experience

If you're trying to edit a given field in a model, Prisma Studio made it quite easy. However, if you're trying to edit every field in a given row, it could get quite annoying to keep scrolling left to right. Our new edit sidebar resolves that with the ability to edit all fields for a given row at once.

Clean up at the click of a button

When editing a number of models, it can get difficult to get back to a clean slate. In the new Prisma Studio, we've added a "Close all" button that puts you back to a fresh start.

Add limit to updateMany() and deleteMany()

Previously, limit has not existed as a valid option in top level updateMany() and deleteMany() queries. In 6.3.0 limit is now available in these queries, bringing their features more in line with other query types.

You can use limit like the following:

await prisma.user.deleteMany({
  where: { column: 'value' },
  limit: 100,
});

This will limit the number of deleted users to 100 at maximum.

Sort generator fields deterministically

In previous version of Prisma ORM, the fields inside of a generator block in your Prisma Schema were not deterministically sorted. This could lead to cases where prisma db pull could lead to re-ordering of fields.

In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first prisma db pull after you upgrade, but it will remain consistent afterwards.

Replace NOT IN with NOT EXISTS for PostgreSQL relation filters

In previous versions of Prisma ORM, when using the none or some relation filters, the SQL queries generated used NOT IN. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of IN with EXISTS in order to improve query performance.

A special thank you

We'd like to extend our heartfelt thanks to @​loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #​19249 and #​17303. Their insights and partnership have been invaluable in improving our product.

If your team could benefit from dedicated support and tailored solutions, learn more about our enterprise support plan.

Fixes and improvements

Prisma Client

• Add take or limit to updateMany() & deleteMany()

Prisma

• Prisma interactive transaction ignores DB exception on commit (with triggers)
• prisma db pull non-deterministically sorts generator fields
• no entry found for key error on views<->model relations
• Adding onUpdate data to the DMMF in @prisma/generator-helper

Credits

Huge thanks to @​WhyAsh5114 for their contributions to this release!

sapphiredev/utilities (@​sapphire/utilities)

v3.18.2

Compare Source

🐛 Bug Fixes

• utilities: Ensure consistent typing for objectEntries, objectKeys and objectValues (598c24a) (#​857 by @​GeniusTimo)

docker/build-push-action (docker/build-push-action)

v6.15.0

Compare Source

• Bump @​docker/actions-toolkit from 0.55.0 to 0.56.0 in https://github.com/docker/build-push-action/pull/1330

Full Changelog: docker/build-push-action@v6.14.0...v6.15.0

v6.14.0

Compare Source

• Bump @​docker/actions-toolkit from 0.53.0 to 0.55.0 in https://github.com/docker/build-push-action/pull/1324

Full Changelog: docker/build-push-action@v6.13.0...v6.14.0

v6.13.0

Compare Source

• Bump @​docker/actions-toolkit from 0.51.0 to 0.53.0 in https://github.com/docker/build-push-action/pull/1308

Full Changelog: docker/build-push-action@v6.12.0...v6.13.0

v6.12.0

Compare Source

• Bump @​docker/actions-toolkit from 0.49.0 to 0.51.0 in https://github.com/docker/build-push-action/pull/1300

Full Changelog: docker/build-push-action@v6.11.0...v6.12.0

v6.11.0

Compare Source

• Handlebar defaultContext support for build-contexts input by @​crazy-max in https://github.com/docker/build-push-action/pull/1283
• Bump @​docker/actions-toolkit from 0.46.0 to 0.49.0 in https://github.com/docker/build-push-action/pull/1281

Full Changelog: docker/build-push-action@v6.10.0...v6.11.0

v6.10.0

Compare Source

• Add call input to set method for evaluating build by @​crazy-max in https://github.com/docker/build-push-action/pull/1265
• Bump @​actions/core from 1.10.1 to 1.11.1 in https://github.com/docker/build-push-action/pull/1238
• Bump @​docker/actions-toolkit from 0.39.0 to 0.46.0 in https://github.com/docker/build-push-action/pull/1268
• Bump cross-spawn from 7.0.3 to 7.0.6 in https://github.com/docker/build-push-action/pull/1261

Full Changelog: docker/build-push-action@v6.9.0...v6.10.0

docker/login-action (docker/login-action)

v3.4.0

Compare Source

• Bump @​actions/core from 1.10.1 to 1.11.1 in https://github.com/docker/login-action/pull/791
• Bump @​aws-sdk/client-ecr to 3.766.0 in https://github.com/docker/login-action/pull/789 https://github.com/docker/login-action/pull/856
• Bump @​aws-sdk/client-ecr-public to 3.758.0 in https://github.com/docker/login-action/pull/789 https://github.com/docker/login-action/pull/856
• Bump @​docker/actions-toolkit from 0.35.0 to 0.57.0 in https://github.com/docker/login-action/pull/801 https://github.com/docker/login-action/pull/806 https://github.com/docker/login-action/pull/858
• Bump cross-spawn from 7.0.3 to 7.0.6 in https://github.com/docker/login-action/pull/814
• Bump https-proxy-agent from 7.0.5 to 7.0.6 in https://github.com/docker/login-action/pull/823
• Bump path-to-regexp from 6.2.2 to 6.3.0 in https://github.com/docker/login-action/pull/777

Full Changelog: docker/login-action@v3.3.0...v3.4.0

docker/setup-buildx-action (docker/setup-buildx-action)

v3.10.0

Compare Source

• Bump @​docker/actions-toolkit from 0.54.0 to 0.56.0 in https://github.com/docker/setup-buildx-action/pull/408

Full Changelog: docker/setup-buildx-action@v3.9.0...v3.10.0

v3.9.0

Compare Source

• Bump @​docker/actions-toolkit from 0.48.0 to 0.54.0 in https://github.com/docker/setup-buildx-action/pull/402 https://github.com/docker/setup-buildx-action/pull/404

Full Changelog: docker/setup-buildx-action@v3.8.0...v3.9.0

v3.8.0

Compare Source

• Make cloud prefix optional to download buildx if driver is cloud by @​crazy-max in https://github.com/docker/setup-buildx-action/pull/390
• Bump @​actions/core from 1.10.1 to 1.11.1 in https://github.com/docker/setup-buildx-action/pull/370
• Bump @​docker/actions-toolkit from 0.39.0 to 0.48.0 in https://github.com/docker/setup-buildx-action/pull/389
• Bump cross-spawn from 7.0.3 to 7.0.6 in https://github.com/docker/setup-buildx-action/pull/382

Full Changelog: docker/setup-buildx-action@v3.7.1...v3.8.0

prettier/eslint-config-prettier (eslint-config-prettier)

v10.1.1

Compare Source

Patch Changes

• #​309 eb56a5e Thanks @​JounQin! - fix: separate the /flat entry for compatibility

  For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.

  See also #​308

  // before
  import eslintConfigPrettier from "eslint-config-prettier";
  
  // after
  import eslintConfigPrettier from "eslint-config-prettier/flat";

v10.1.0

Compare Source

Minor Changes

• #​306 56e2e34 Thanks @​JounQin! - feat: migrate to exports field

v10.0.3

Compare Source

Patch Changes

• #​294 8dbbd6d Thanks @​FloEdelmann! - feat: add name to config

• #​280 cba5737 Thanks @​zanminkian! - feat: add declaration file

v10.0.2

Compare Source

Patch Changes

• #​299 e750edc Thanks @​Fdawgs! - chore(package): explicitly declare js module type

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.2.6

Compare Source

Patch Changes

• #​723 1451176 Thanks @​renovate! - fix(deps): bump synckit to v0.11.0

v5.2.5

Compare Source

Patch Changes

• #​721 4f5513d Thanks @​JounQin! - fix: clarify correct eslint-config-prettier peer range

v5.2.4

Compare Source

Patch Changes

• #​715 b8cfe56 Thanks @​JounQin! - chore: hourcekeeping, bump all (dev) deps

lint-staged/lint-staged (lint-staged)

v15.5.0

[Compare Source](https://redirect.github.com

---

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.