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.6.1					devDependencies	patch
@commitlint/config-conventional (source)	^19.5.0 -> ^19.6.0					devDependencies	patch
@discordjs/builders (source)	^1.9.0 -> ^1.10.0					dependencies	patch
@prisma/client (source)	^6.0.0 -> ^6.3.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.1					dependencies	patch
@skyra/http-framework (source)	^2.1.0 -> ^2.2.0					dependencies	patch
@types/node (source)	^22.8.6 -> ^22.12.0					devDependencies	minor
docker/build-push-action	v6.9.0 -> v6.13.0					action	minor
docker/setup-buildx-action	v3.7.1 -> v3.8.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.13.1					volta	minor
prettier (source)	^3.3.3 -> ^3.4.2					devDependencies	patch
prisma (source)	^6.0.0 -> ^6.3.0					devDependencies	minor
tslib (source)	^2.8.0 -> ^2.8.1					dependencies	patch
yarn (source)	4.5.1 -> 4.6.0					packageManager	minor

---

Release Notes

prisma/prisma (@​prisma/client)

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

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!

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

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.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.13.1

Compare Source

v22.13.0

Compare Source

v22.12.0

Compare Source

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.