fix(deps): update all non-major dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update
@commitlint/cli (source)	^20.1.0 → ^20.5.3			devDependencies	minor
@commitlint/config-conventional (source)	^20.0.0 → ^20.5.3			devDependencies	minor
@discordjs/builders (source)	^1.9.0 → ^1.14.1			dependencies	minor
@prisma/client (source)	^6.0.0 → ^6.19.3			dependencies	minor
@sapphire/eslint-config (source)	^5.0.5 → ^5.0.6			devDependencies	patch
@sapphire/iterator-utilities (source)	^2.0.0 → ^2.0.1			dependencies	patch
@sapphire/result (source)	^2.6.6 → ^2.8.0			dependencies	minor
@sapphire/time-utilities (source)	^1.7.12 → ^1.7.14			dependencies	patch
@sapphire/ts-config (source)	^5.0.1 → ^5.0.3			devDependencies	patch
@sapphire/utilities (source)	^3.17.0 → ^3.18.2			dependencies	patch
@skyra/env-utilities (source)	^2.0.0 → ^2.0.1			dependencies	patch
@skyra/http-framework (source)	^2.1.0 → ^2.2.1			dependencies	patch
@skyra/http-framework-i18n (source)	^1.2.0 → ^1.2.1			dependencies	patch
@skyra/logger (source)	^2.0.3 → ^2.0.4			dependencies	patch
@skyra/safe-fetch (source)	^1.1.3 → ^1.1.4			dependencies	patch
@skyra/shared-http-pieces (source)	^1.2.2 → ^1.2.3			dependencies	patch
@skyra/start-banner (source)	^2.0.1 → ^2.0.2			dependencies	patch
@types/node (source)	^24.10.0 → ^24.13.3			devDependencies	minor
docker/build-push-action	v6.9.0 → v6.19.2			action	minor
docker/login-action	v3.3.0 → v3.7.0			action	minor
docker/setup-buildx-action	v3.7.1 → v3.12.0			action	minor
eslint-config-prettier	^10.0.1 → ^10.1.8			devDependencies	minor
eslint-plugin-prettier	^5.2.1 → ^5.5.6			devDependencies	minor
lint-staged	^16.0.0 → ^16.4.0			devDependencies	minor
node (source)	24.11.0 → 24.18.1			volta	minor
prettier (source)	^3.3.3 → ^3.9.6			devDependencies	minor
prisma (source)	^6.0.0 → ^6.19.3			devDependencies	minor
tslib (source)	^2.8.0 → ^2.8.1			dependencies	patch
yarn (source)	4.5.1 → 4.18.0			packageManager	minor

---

Release Notes

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

v20.5.3

Compare Source

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

v20.5.2

Compare Source

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

v20.5.0

Compare Source

Bug Fixes

• cli: validate that --cwd directory exists before execution (#​4658) (cf80f75), closes #​4595

20.4.4 (2026-03-12)

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

20.4.3 (2026-03-03)

Bug Fixes

• footer parser does not escape special chars for regex #​4560 (#​4634) (8ff7c7f)

20.4.2 (2026-02-19)

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

20.4.1 (2026-02-02)

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

v20.4.4

Compare Source

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

v20.4.3

Compare Source

Bug Fixes

• footer parser does not escape special chars for regex #​4560 (#​4634) (8ff7c7f)

v20.4.2

Compare Source

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

v20.4.1

Compare Source

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

v20.4.0

Compare Source

Features

• upgrade conventional commit packages #​4082 (#​4597) (3aaf0a6)

20.3.1 (2026-01-08)

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

v20.3.1

Compare Source

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

v20.3.0

Compare Source

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

v20.2.0

Compare Source

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

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

v20.5.3

Compare Source

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

v20.5.0

Compare Source

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

20.4.4 (2026-03-12)

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

20.4.3 (2026-03-03)

Bug Fixes

• footer parser does not escape special chars for regex #​4560 (#​4634) (8ff7c7f)

20.4.2 (2026-02-19)

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

20.4.1 (2026-02-02)

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

v20.4.4

Compare Source

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

v20.4.3

Compare Source

Bug Fixes

• footer parser does not escape special chars for regex #​4560 (#​4634) (8ff7c7f)

v20.4.2

Compare Source

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

v20.4.1

Compare Source

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

v20.4.0

Compare Source

Features

• upgrade conventional commit packages #​4082 (#​4597) (3aaf0a6)

20.3.1 (2026-01-08)

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

v20.3.1

Compare Source

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

v20.3.0

Compare Source

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

v20.2.0

Compare Source

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

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

v1.14.1

Compare Source

Bug Fixes

• Actually accept rest in RadioGroup/CheckBoxGroupBuilder#setOptions (#​11472) (6e45ddc)

v1.14.0

Compare Source

Documentation

• builders: Edited docs to correctly link to splice (#​11430) (ec5d921)

Features

• builders: Add checkbox, checkboxgroup, and radiogroup builders (#​11410) (ca7719e)

v1.13.1

Compare Source

Bug Fixes

• Adjust label predicates (#​11318) (61251cf)

Documentation

• Container: Update example usage (e777938)

v1.13.0

Compare Source

Features

• V1 builders file uploads support (#​11196) (1417c49)

Testing

• Fix type error (f780c6a)

v1.12.2

Compare Source

Bug Fixes

• Assertions: Literal default values (43362c9)

v1.12.1

Compare Source

Bug Fixes

• builders: Text display component support for modals (#​11155) (99b8436)

v1.12.0

Compare Source

Features

• builders: Modal select menus in builders v1 (#​11138) (ac683b9)

v1.11.3

Compare Source

Bug Fixes

• contextMenuCommands: Remove regular expression validation (#​10996) (4906aae)

v1.11.2

Compare Source

v1.11.1

Compare Source

v1.11.0

Compare Source

Features

• Components v2 in builders v1 (#​10787) (118e682)

v1.10.1

Compare Source

Bug Fixes

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

prisma/prisma (@​prisma/client)

v6.19.3

Compare Source

Today, we are issuing a 6.19.3 patch release in the Prisma 6 release line. It updates the effect dependency to resolve a security vulnerability.

Changes:
#​29416

v6.19.2

Compare Source

Today, we are issuing a 6.19.2 patch release in the Prisma 6 release line. It fixes an issue with Prisma Accelerate support in some edge runtime configurations when the @prisma/client/edge entrypoint is not being used.

Changes:

• #​28934

v6.19.1

Compare Source

v6.19.0

Compare Source

v6.18.0

Compare Source

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'),
    }
});

• #​28291 Support multiple Prisma instances with different providers
• #​28305 Add env helper function
• #​28266 Add support for js or classic as engine types in prisma.config
• #​28139 Map Bytes to Uint8Array depending on Typescript version

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.

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

v6.17.1

Compare Source

Today, we are issuing a patch release to address a regression in v6.17.0 that affected diffing of unsupported types, leading to unnecessary or incorrect changes when creating new migrations or running db pull. This update is recommended for all users who have any fields marked as Unsupported in their schema files.

Changes

• prisma/prisma-engines#5633

v6.17.0

Compare Source

Today, we are excited to share the 6.17.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 number of bug fixes and improvements to Prisma ORM.

Bug fixes and improvements

• Added support for Entra ID (ActiveDirectory) authentication parameters for the MS SQL Server driver adapter. For example, you can use the config object to configure DefaultAzureCredential:

  import { PrismaMssql } from '@​prisma/adapter-mssql'
  import { PrismaClient } from '@​prisma/client'
  
  const config = {
    server: 'localhost',
    port: 1433,
    database: 'mydb',
    authentication: {
      type: 'azure-active-directory-default',
    },
    options: {
      encrypt: true,
    },
  }
  
  const adapter = new PrismaMssql(config)
  const prisma = new PrismaClient({ adapter })

  Learn more in this PR.
• Relaxed the support package range for @opentelemetry/instrumentation to be compatible with ">=0.52.0 <1". Learn more in this PR.
• Added Codex CLI detection, ensuring dangerous Prisma operations are not executed by Codex without explicit user consent. Learn more in this PR.
• Fixed JSON column handling when using a MariaDB database. Learn more in this PR.
• Restored the original behaviour of group-by aggregations where they would refer to columns with explicit table names which fixes a regression that would result in ambiguous column errors. Learn more in this PR.

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:

New usage workspace metrics available in your Console Dashboard

The Dashboard in your Prisma Console account now displays new metrics about your Prisma Postgres usage:

• Key metrics
  • Estimated upcoming invoice
  • Total storage used
  • Total DBs
• Overall usage
  • Cumulative operations
  • Operations per day

Using Prisma Postgres with any tool is ready for production

Previously, the only way to connect to Prisma Postgres was using Prisma ORM. That combination is great because it gives you connection pooling, global caching and overall an amazing DX.

That being said, we understand that preferences vary and some developers prefer to use plain SQL or lower-level query builders in their applications. As of this release, these ways for connecting to Prisma Postgres are now officially generally available and can be used in your production apps!

You can connect using Drizzle, Kysely, TypeORM, psql, or any other Postgres-compatible library, database migration tools like Atlas or interfaces like DBeaver, Postico, and more.

📚 Learn more in the docs.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

v6.16.3

Compare Source

Today, we are issuing a 6.16.3 patch release focused on bug fixes.

🛠 Fixes

• Prisma Client (prisma-client generator): fixed missing JSON null type definitions (JsonNull, DbNull, AnyNull) in the browser.ts entrypoint. (#​28186)

• Prisma Migrate: don't add the default schema (namespace) to the generated migrations unless it was specified explicitly in the schema file. This restores the pre-6.13.0 behaviour that was inadvertently changed with enabling multi-schema support by default. Users who rely on database schemas for multi-tenancy can now again use the same migration files for all of their schemas. (prisma/prisma-engines#5614)

• Prisma Client: enabled negative take with findFirst again. (prisma/prisma-engines#5616 — contributed by @​jay-l-e-e)

• Prisma Accelerate: aligned the behaviour of the new Rust-free client with Query Engine to handle self-signed certificates consistently and ensure backward compatibility. (#​28134)

• @prisma/adapter-mariadb: fixed error event listeners leak. (#​28177 — contributed by @​Tiaansu)

⚠️ Known Limitation: JSON null types in browser builds

The fix introduces the missing types, but the singleton instances differ between the client and browser entrypoints of the generated client. This means that values like Prisma.JsonNull imported from browser cannot yet be assigned to fields expected from the client entrypoint, and vice versa. This results in confusing TypeScript errors if you mix them. A follow-up improvement is planned to unify these utility types across entrypoints.

v6.16.2

Compare Source

Today, we are issuing a 6.16.2 patch release.

Bug fixes

• In Prisma ORM 6.16.0, we've enabled usage of the new engineType = client with Prisma Postgres, but our validation rules permitted invalid combinations of Prisma Postgres URLs and driver adapters. This now produces a clear error message indicating Prisma Postgres URLs and driver adapters are mutually exclusive.
• In the previous minor release, we've included a change that calls unref() on NodeJS timers to prevent them from keeping the NodeJS event loop active. This change unintentionally affected non-NodeJS runtimes like workerd, where it has resulted in runtime errors. This behavior has been made conditional to prevent these runtime errors.

v6.16.1

Compare Source

Today, we are issuing a 6.16.1 patch release.

Bug fixes

• In Prisma ORM 6.16.0, the driverAdapters and queryCompiler features were stabilized, but leftover code in the prisma-client-ts generator required them to still be specified in edge runtimes. This has now been fixed, runtimes like workerd and vercel-edge no longer require these preview features.

v6.16.0

Compare Source

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

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

Prisma ORM

This section contains all the updates made in Prisma ORM v6.16.0.

Rust-free ORM and driver adapters are Generally Available

Eight months ago, we published our ORM manifesto with the first hint that we're going to remove the Rust-based query engine from Prisma ORM:

We're addressing this by migrating Prisma's core logic from Rust to TypeScript and redesigning the ORM to make customization and extension easier.

After a lot of hard work and feedback from the community, we're incredibly excited to share that the migration has been completed and you can now use Prisma ORM without its Rust engine in your production apps. 🎉 This is a major milestone in the history of Prisma ORM and comes with a lot of benefits:

• Reduced bundle size by ~90%
• Faster queries (check out our latest benchmarks)
• Lower CPU footprint
• Less deployment complexity
• Easier to make open-source contributions

… and overall a much better DX since you don't need to worry about the extra binary in your generated Prisma Client code any more.

While the Rust-free ORM will become the default in Prisma ORM v7 soon, for now you still need to opt-into using it:

1. Configure the generator block in your Prisma schema:

   generator client {
     provider   = "prisma-client" // (or "prisma-client-js") 
     output     = "../src/generated/prisma"
     engineType = "client"
   }

   Note: If you tried the Rust-free ORM before, you can now also drop the queryCompiler and driverAdapter feature flags from the previewFeatures array. And if you used binaryTargets, you can also get rid of these.
2. Install the driver adapter for your database, e.g. to use pg for PostgreSQL:

   npm install @​prisma/adapter-pg
   

3. Finally, you can instantiate PrismaClient using the PrismaPg driver adapter as follows:

   import { PrismaClient } from './generated/prisma'
   import { PrismaPg } from '@​prisma/adapter-pg'
   
   const adapter = new PrismaPg({ connectionString: env.DATABASE_URL })
   const prisma = new PrismaClient({ adapter })
   
   // ... send queries using `prisma` like before

📚 To learn more and see instructions for all other supported databases, check out the documentation.

The Rust-free version of Prisma ORM has been thoroughly tested with the prisma-client generator (see below), not with prisma-client-js. Use the old generator at your discretion.

New ESM-first prisma-client generator is Generally Available

Another major milestone has been achieved in this release: The new, flexible and ESM-first prisma-client generator is ready for production too. Here's a quick overview of its main benefits:

• No more magic generation into node_modules; generated code is fully under control by the developer
• ESM-compatible by default
• Flexible configuration for specific runtimes (Node.js, Deno, Bun, Cloudflare, …)

generator client {
  // Required
  provider = "prisma-client"
  output   = "../src/generated/prisma"

  // Optional
  engineType             = "client"
  runtime                = "nodejs"
  moduleFormat           = "esm"
  generatedFileExtension = "ts"
  importFileExtension    = "ts"
}

In addition to making it production-ready, we also made some changes to the prisma-client generator:

• removed Prisma.validator; you can use TypeScript native satisfies keyword instead
• created a new ./generared/prisma/browser entrypoint for importing types in browser environments

If you want to try out the new generator with your favorite framework, check out one of our ready-to-run examples (e.g. for Next.js, Nuxt or React Router).

📚 Learn more in the docs.

Type check performance optimizations

Runtime performance is not the only performance category that matters. In fact, when it comes to DX, type checking performance is equally important: if your TypeScript types become too complex and the compiler needs to do too much work (e.g. inferring types), it may slow down your editor, lead to laggy auto-completion or prevent jump-to-definition from working.

We've worked with TypeScript expert David Blass to find ways for improving the type checking performance in Prisma ORM and created benchmarks comparing the type checking performance with Drizzle.

You can read about the results here: Why Prisma ORM Checks Types Faster Than Drizzle

Deprecating the postgresqlExtensions Preview feature

We're deprecating the postgresqlExtensions Preview feature. Note that this doesn't mean that you can't use extensions with Prisma ORM any more. Instead of setting the Preview feature, you can install extensions manually with a customized migration via the --create-only flag:

npx prisma migrate dev --name add-extension --create-only

You can then install an extension with plain SQL in the newly created, empty migration file:

CREATE EXTENSION IF NOT EXISTS "pgcrypto";

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:

Manage OAuth apps in Prisma Console

In Prisma Console, you can now manage all of the 3rd party applications that you've granted access to perform actions on behalf of yourself in your Prisma Console account. Find the 🧩 Integrations tab in the sidenav to see which applications currently have access.

Rust-free Prisma ORM with Prisma Accelerate and Prisma Postgres

With this release, the Rust-free Prisma ORM (Query Compiler) can now be used together with Prisma Postgres and also Prisma Accelerate. This means you can take advantage of connection pooling and caching while using the new TypeScript-based ORM architecture.

To enable it, update your Prisma schema:

generator client {
  provider   = "prisma-client"
  output     = "../src/generated/prisma"
  engineType = "client"
}

We'd love for you to try this out and share your feedback as we prepare for General Availability. Please open an issue on GitHub if you encounter any problems or have suggestions.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

v6.15.0

Compare Source

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

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

Highlights

AI safety guardrails for destructive commands

Prisma ORM now includes built-in safety checks that protect against destructive commands when triggered by AI coding assistants. The CLI can recognize when it is being executed by popular AI agents such as Claude Code, Gemini CLI, Qwen Code, Cursor, Aider and Replit.

If a command like prisma migrate reset --force is attempted, Prisma ORM will prompt for explicit confirmation before proceeding.

This feature ensures that irreversible operations which drop and recreate the database are not executed automatically by an AI tool. Prisma ORM is the first ORM to provide this level of protection, making it safer to use AI-assisted development while working with your databases.

📚 Learn more in the docs.

prisma-client: runtime improvements and schema flexibility

We simplified Prisma ORM by making the runtime options for the Prisma Client more consistent and easier to understand. Previously there were several overlapping aliases which created confusion. With this release we simplified the inputs while keeping support for all the major environments you might be targeting.

Changes include:

• node has been removed, use runtime = "nodejs" instead
• deno-deploy has been removed, use runtime = "deno" instead
• vercel has been replaced by the new runtime = "vercel-edge"
• edge-light is now just an alias for vercel-edge
• nodejs, deno, and bun now share the same internal code path, while still keeping their separate input values for clarity
• The VS Code extension has been updated to reflect these changes

The updated list of supported runtimes is now:

`nodejs

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 12pm on Sunday"
• 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.