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.7.1					devDependencies	minor
@commitlint/config-conventional (source)	^19.5.0 -> ^19.7.1					devDependencies	minor
@discordjs/builders (source)	^1.9.0 -> ^1.10.1					dependencies	patch
@prisma/client (source)	^6.0.0 -> ^6.4.1					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.13.4					devDependencies	minor
docker/build-push-action	v6.9.0 -> v6.14.0					action	minor
docker/setup-buildx-action	v3.7.1 -> v3.9.0					action	minor
eslint-plugin-prettier	^5.2.1 -> ^5.2.3					devDependencies	patch
lint-staged	^15.2.10 -> ^15.4.3					devDependencies	patch
node (source)	22.11.0 -> 22.14.0					volta	minor
prettier (source)	^3.3.3 -> ^3.5.1					devDependencies	minor
prisma (source)	^6.0.0 -> ^6.4.1					devDependencies	minor
tslib (source)	^2.8.0 -> ^2.8.1					dependencies	patch
yarn (source)	4.5.1 -> 4.6.0					packageManager	minor

---

Release Notes

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

v19.7.1

Compare Source

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

conventional-changelog/commitlint (@​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.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.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/setup-buildx-action (docker/setup-buildx-action)

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

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

v15.4.3

Compare Source

Patch Changes

• #​1512 cbfed1d Thanks @​tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

v15.4.2

Compare Source

Patch Changes

• #​1509 8827ebf Thanks @​iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

nodejs/node (node)

v22.14.0

Compare Source

v22.13.1

Compare Source

v22.13.0

Compare Source

v22.12.0

Compare Source

prettier/prettier (prettier)

v3.5.1

Compare Source

diff

Fix CLI crash when cache for old version exists (#​17100 by @​sosukesuzuki)

Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.

Support dockercompose and github-actions-workflow in VSCode (#​17101 by @​remcohaszing)

Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.

v3.5.0

Compare Source

diff

🔗 Release Notes

yarnpkg/berry (yarn)

v4.6.0

Compare Source

v4.5.3

Compare Source

v4.5.2

Compare Source

---

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.