fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update
@prisma/client (source)	6.8.2 -> 6.12.0			dependencies	minor
@sapphire/decorators (source)	6.1.1 -> 6.2.0			dependencies	minor
@sapphire/framework (source)	5.3.5 -> 5.3.6			dependencies	patch
@sapphire/plugin-logger (source)	4.0.2 -> 4.1.0			dependencies	minor
@swc/core (source)	1.11.29 -> 1.13.2			devDependencies	minor
@types/bun (source)	1.2.14 -> 1.2.19			devDependencies	patch
@types/node (source)	22.15.23 -> 22.16.5			devDependencies	minor
akhileshns/heroku-deploy	v3.12.14 -> v3.14.15			action	minor
discord.js (source)	14.19.3 -> 14.21.0			dependencies	minor
node (source)	20.10.0 -> 20.19.4			engines	minor
oven/bun	1.2.13-alpine -> 1.2.19-alpine			final	patch
oven/bun	1.2.13-alpine -> 1.2.19-alpine			stage	patch
prettier (source)	3.5.3 -> 3.6.2			devDependencies	minor
prisma (source)	6.8.2 -> 6.12.0			dependencies	minor
undici (source)	7.10.0 -> 7.12.0			dependencies	minor

---

Release Notes

prisma/prisma (@​prisma/client)

v6.12.0

Compare Source

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

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

Highlights

ESM-compatible prisma-client generator now in Preview

We’re excited to share that our new and more flexible prisma-client generator is moving into Preview! As a reminder, here’s what it looks like:

generator client {
  // Required
  provider = "prisma-client" // no `-js` at the end!
  output   = "../src/generated/prisma"

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

This new generator eliminates any headaches that you may have experienced due to magical code generation into node_modules and gives you full control over the generated Prisma Client code. With it moving into Preview, we hope that even more of you will try it out and share your feedback with us!

Note: The prisma-client generator will become the default in Prisma v7, replacing the current prisma-client-js generator.

In addition to moving it into Preview, we also created a couple of new ready-to-run examples to help you get started with the new generator and your favorite framework:

• React Router + Vite + Cloudflare
• React Router + Vite + Node.js
• Nuxt 3 + Vite + Nitro
• Deno Deploy

📚 Learn more in the docs.

Specify views and migrations folder locations in prisma.config.ts (Early Access)

As we’re getting closer to the General Availability release of prisma.config.ts, we’re adding more capabilities to it. In previous versions, the Prisma CLI implicitly used to infer the location for migration and SQL view definition files based on the location of the Prisma schema. In this release, we’re adding two new fields (migrations and views) to give you more flexibility and clarity on how to locate these files:

// prisma.config.ts
export default defineConfig({
  earlyAccess: true,
  migrations: {
    path: './db/migrations'
  },
  views: {
    path: './db/views'
  }
  // ...
})

📚 Learn more in the docs.

v6.11.1

Compare Source

Today, we are issuing a 6.11.1 patch release.

Bug fixes

• In Prisma ORM version 6.11.0, we shipped a bug fix for Prisma that allows using Prisma Postgres with direct TCP connections with Prisma Driver Adapters. This fix, however, required refactoring the of the Prisma Client initialization logic, and while several test cases were added, an edge case was missing, causing https://github.com/prisma/prisma/issues/27569.
  Namely, using @prisma/client with @prisma/extension-accelerate on a prisma+postgres://... connection string, while generating the Prisma Client definitions via prisma generate, resulted in a PrismaClientInitializationError.

  This is now fixed, so we highly recommend upgrading to version 6.11.1.

  Reminder: when using Prisma Accelerate, we highly encourage you to generate your Prisma Client definitions via prisma generate --no-engine.

• We've fixed an issue that would occur when using arrays as aggregation fields with the query compiler. These queries would fail with a confusing data mapping error. They should now work as expected.

v6.11.0

Compare Source

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

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

Highlights

Prisma ORM without Rust engines for MySQL/MariaDB, Neon & CockroachDB (Preview)

We are in the process of removing the Rust engines from Prisma ORM. This week, we're adding Preview support for the Rust-free Prisma ORM version for MySQL via a new @prisma/adapter-mariadb driver adapter, as well as for Neon and CockroachDB via the already existing @prisma/adapter-neon and @prisma/adapter-pg adapters.

Note: The mariadb driver is compatible with all MySQL databases. It's the recommended option to use MySQL with Prisma ORM when using driver adapters.

To use it, enable the queryCompiler and driverAdapters feature flags on your generator block, install the driver adapter for your database and start querying!

generator client {
  provider        = "prisma-client-js" // or `prisma-client`
  output          = "../generated/prisma"
  previewFeatures = ["queryCompiler", "driverAdapters"]
}

📚Learn more in the docs.

Stop and remove local Prisma Postgres instances via CLI

You can start a local Prisma Postgres instance using the prisma dev --name mydb command or via the Prisma VS Code extension UI.

If you start a local instance via the Prisma CLI, you can simply kill the process to stop the instance. However, when you start instances via the VS Code extension UI, you could also only stop them via the UI—not via the CLI.

This changes in this release: You can now also stop local Prisma Postgres instances and remove them from your file system via the Prisma CLI:

• prisma dev stop <globs>: Stops one or more local Prisma Postgres instances
• prisma dev rm <globs>: Removes one or more local Prisma Postgres instances from your file system

📚Learn more in the docs.

Ready-to-run examples for new prisma-client generator

Our new prisma-client generator is more flexible, provides more control about the generated code, works with various JS runtimes and comes with ESM support out-of-the-box.

To make it easier for you to try it out, we created a few ready-to-run example projects so you can see the new generator in action:

• nextjs-starter-webpack
• nextjs-starter-turbopack
• neextjs-starter-webpack-monorepo
• nextjs-starter-webpack-with-middleware

Bug fixes in VS Code embedded Prisma Studio

Have you already seen the new look of Prisma Studio when it's embedded directly in VS Code via the Prisma VS Code extension? In this release, we fixed a few bugs that you all have reported:

• Fixed an issue with writing and deleting from tables with UUIDs
• Fixed an issue with saving data in fullscreen mode
• Fixed an issue with updating the schema when the refresh button is clicked

Let us know in case you hit any snags with Prisma ORM by opening a new issue.

Other news

Embed Prisma Studio in your own tools and projects

If you're using Prisma Postgres (yourself or by offering it to your own users), you can now embed Prisma Studio to offer an amazing data editing experience to your users via the @prisma/studio-core npm package.

Try out the demo that shows how to integrate Prisma Studio in your own apps!

Predict your Prisma Postgres bill with our new Pricing Calculator

Prisma Postgres comes with a pricing model that seems too simple to be true: You're charged based on storage and operations—not CPU, compute hours or any other resource-based metrics.

While it's simple, it may feel unfamiliar because it's so different from existing pricing models. To understand how much you'd pay for Prisma Postgres running your app, you can now use our Pricing Calculator. Put in the predicted storage and number of operations to see how much you're going to be charged on each plan.

Prisma Postgres now available for all Postgres templates in Vercel Marketplace

On vercel.com/templates, you can find lots of one-click-deploy application templates! We recently worked with the Vercel team to get Prisma Postgres working with all templates requiring a PostgreSQL database, for example:

• Next.js SaaS Starter with Drizzle ORM
• Postgres SvelteKit Starter with Postgres.js
• Next.js + PostgreSQL Auth Starter with Drizzle ORM
• … and a lot more

Connecting to Prisma Postgres with any tool is now faster

We recently enabled the option to connect to Prisma Postgres with any tool via direct TCP connections. In this release, we have reduced the connection latency so your first request is now faster.

New region for Prisma Postgres: Frankfurt (eu-central-1)

We keep expanding Prisma Postgres availability across the globe! After having added San Francisco just a few weeks ago, we're now adding Frankfurt based on another poll we ran on X. Here are all the regions where you can spin up Prisma Postgres instances today:

• eu-central-1: Frankfurt (new!)
• eu-west-3: Paris
• us-west-1: San Francisco
• us-east-1: North Virginia
• ap-northeast-1: Tokyo
• ap-southeast-1: Singapore

Keep an eye on our X account to take part in the poll and vote for the next availability zone of Prisma Postgres!

v6.10.1

Compare Source

Today, we are issuing a 6.10.1 patch release.

Bug fixes

In Prisma ORM version 6.10.0, we shipped a bug fix for Prisma Migrate that ensured we always gracefully closed PostgreSQL connections by sending the Terminate message and not just abruptly closing the TCP connection. This fix was incomplete because it didn't work on Windows, which is now fixed. We highly recommend upgrading to version 6.10.1 if you are using Windows.

We also recommend upgrading to this version if you are currently using local Prisma Postgres via the prisma dev command with an ORM version older than 6.10.x.

Performance improvements

The queryCompiler preview feature recently introduced a performance regression related to in-memory joins in TypeScript-based query execution (users who use the queryCompiler and the relationJoins preview features together were not affected, unless using relationLoadStrategy: "query"). This has now been fixed, leading to significant performance improvements: in our Query Compiler benchmarks, we are seeing up to 500x performance improvement compared to the previous implementation in the TypeScript-based query executor, or up to 10–20x performance improvement compared to the Rust-based Query Engine.

Other news

Please see the release notes for Prisma ORM 6.10.0 for other recent news and announcements.

v6.10.0

Compare Source

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

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

Highlights

No Rust engines for MS SQL Server & PlanetScale (Preview)

We are in the process of removing the Rust engines from Prisma ORM. If you want to try this, you can configure your generator like this:

generator client {
  provider        = "prisma-client-js" // or `prisma-client`
  output          = "../generated/prisma"
  previewFeatures = ["queryCompiler", "driverAdapters"]
}

In this release, we are excited to move the queryCompiler (which enables using Prisma ORM without Rust engines) into Preview for MS SQL Server and PlanetScale (via the new @prisma/adapter-mssql and existing @prisma/adapter-planetscale driver adapters).

📚Learn more in the docs.

Manage local Prisma Postgres instances in VS Code

We recently released a database management UI as part of the Prisma VS Code extension to enable visual database management workflows for Prisma Postgres. In this release, we added new functionality to it: You can now manage multiple local Prisma Postgres instances via the same UI. To try it, find the Prisma logo in VS Code’s sidebar and start managing your local Prisma Postgres instances (no Docker required).

📚 Learn more in the docs.

Performance improvements for prisma migrate dev

We improved the prisma migrate dev command by optimizing the interactions with the shadow database. Our measurements show a 2x improvement in speed for some databases!

"Push to Cloud": Easily deploy a local Prisma Postgres instance in VS Code

Local Prisma Postgres instances are perfect for development, but how do you go from local to remote once you’re ready to deploy?

The database management UI in VS Code now has a Push to Cloud button that makes it easy to deploy your local Prisma Postgres so that you can connect to it from your deployed applications.

📚 Learn more in the docs.

Support for shard keys on PlanetScale (Preview)

Sharding is a popular technique to scale up when database load grows. As of this release, Prisma ORM supports sharding on PlanetScale natively via the new @shardKey and @@​shardKey attributes in the Prisma schema which you can apply to the fields in your models that should serve as shard keys in your database setup:

// Single-column shard key
model User {
  id     String @​default(uuid())
  region String @​shardKey
}

// Multi-column shard key
model User {
  id         String @​default(uuid())
  country    String
  customerId String
  @​@​shardKey([country, customerId])
}

Note that this requires you to set the shardKeys Preview feature flag on your generator definition:

generator client {
  provider        = "prisma-client-js" // or `prisma-client`
  output          = "../generated/prisma"
  previewFeatures = ["shardKeys"]
}

📚 Learn more in the docs.

Other changes

• We deprecated the pg-worker package. It's not needed any more, you can simply use pg when using Prisma ORM in Cloudflare Workers.
• Entrypoint for new prisma-client generator changed. Learn how this affects imports in the docs.

More news

Local Prisma Postgres now works with any ORM & tool (Early Access)

We recently released direct connections for remote Prisma Postgres so that you can now use it with your favorite ORM or database tool. As of this release, this is also possible for your local Prisma Postgres instances. To try it, run the prisma dev command and use the direct connection string starting with postgres:// in order to connect from any tool.

📚 Learn more in the docs.

Let your favorite AI tool manage Prisma Postgres via remote MCP

We just released a new remote MCP server that helps you manage Prisma Postgres instances! It enables your AI tools to help with these workflows:

• Managing databases and connection strings
• Creating and re-instantiating backups
• Querying databases via plain SQL
• Introspecting database schemas

You can start it using the npx -y mcp-remote https://mcp.prisma.io/mcp command.

📚 Learn more in the docs.

v6.9.0

Compare Source

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

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

Highlights

Prisma ORM without Rust engines for PostgreSQL & SQLite (Preview)

If you've been excited about our work of removing the Rust engines from Prisma ORM but hesitated trying it out because it was in an Early Access (EA) phase, now is a great time for you to get your hands on the Rust-free Prisma ORM version.

This major architectural change has moved from EA into Preview in this release, meaning there are no more know major issues. If you want to try it out, add the queryCompiler and driverAdapters preview feature flags to your generator, install the driver adapter for your database, and get going:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["queryCompiler", "driverAdapters"]
  output          = "../generated/prisma"
}

Now run prisma generate to re-generate Prisma Client. If you didn't use a driver adapter before, you'll need to install, e.g. the one for PostgreSQL:

npm install @​prisma/adapter-pg

Once installed, you can instantiate PrismaClient 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 })

No more hassle with query engines, binary targets and an even smoother experience in serverless and edge environments!

📚 Learn more in the docs.

Major improvements for local Prisma Postgres (Preview)

In the last release, we enabled you to spin up a Prisma Postgres instance locally via the new prisma dev command. Local Prisma Postgres uses PGlite under the hood and gives you an identical experience as you get with a remote Prisma Postgres instance.

This release brings major improvements to this feature:

• Persists your databases across prisma dev invocations.
• Enables you to have multiple local Prisma Postgres instances running at the same time.
• Running prisma init now uses local Prisma Postgres by default.

Try it out and let us know what you think!

📚 Learn more in the docs.

More news

Connect to Prisma Postgres with any ORM (Preview)

Since its GA release, you could only interact with Prisma Postgres using Prisma ORM via a custom connection string.

This has changed now: When setting up a new Prisma Postgres instance, you receive a regular PostgreSQL direct TCP connection string (starting with postgres://...) that lets you connect to it using your favorite tool or database library, including Drizzle, Kysely, TypeORM, and others.

If you want to access Prisma Postgres from a serverless environment, you can also use our new serverless driver (Early Access).

📚 Learn more in the docs.

Automated backup & restore

Prisma Postgres' backup and restore mechanism has seen a major upgrade recently: You can now easily restore any previous backup via the UI in the Prisma Console. Find the new Backups tab when viewing your database and select any backup from the list to restore its state to a previous point in time.

📚 Learn more in the docs.

Prisma's VS Code extension now has a UI to manage Prisma Postgres

If you're using Prisma ORM, chances are that you're using our VS Code extension too. In its latest release, we've added a major new capability to it: A UI for managing databases.

With this new UI, you can:

• Authenticate with the Prisma Console
• Create and delete remote Prisma Postgres instances
• View local Prisma Postgres instances
• View and edit data via an embedded Prisma Studio
• Visualize your database schema

To use the new features, make sure to have the latest version of the Prisma VS Code extension installed and look out for the new Prisma logo in VS Code's Activity Bar.

📚 Learn more in the docs.

New region for Prisma Postgres: San Francisco (us-west-1)

We keep expanding Prisma Postgres availability across the globe! After having added Singapore just a few weeks ago, we're now adding San Francisco based on another poll we ran on X. Here are all the regions where you can spin up Prisma Postgres instances today:

• us-west-1: San Francisco (new!)
• us-east-1: North Virginia
• eu-west-3: Paris
• ap-northeast-1: Tokyo
• ap-southeast-1: Singapore

Keep an eye on our X account to take part in the poll and vote for the next availability zone of Prisma Postgres!

sapphiredev/utilities (@​sapphire/decorators)

v6.2.0

Compare Source

🐛 Bug Fixes

• deps: Update all non-major dependencies (4bc5591) (#​879 by @​renovate[bot])
• deps: Update all non-major dependencies (bc2f01c) (#​869 by @​renovate[bot])

🚀 Features

• decorators: Register application commands decorators (da07d09) (#​877 by @​yuansheng1549)

sapphiredev/framework (@​sapphire/framework)

v5.3.6

Compare Source

🐛 Bug Fixes

• dependencies: Update @​sapphire/pieces (2f251c0)

sapphiredev/plugins (@​sapphire/plugin-logger)

v4.1.0

Compare Source

🐛 Bug Fixes

• deps: Update all non-major dependencies (d23894e) (#​752 by @​renovate[bot])
• deps: Update all non-major dependencies (5106865) (#​742 by @​renovate[bot])
• deps: Update all non-major dependencies (cc47e19) (#​705 by @​renovate[bot])
• deps: Update all non-major dependencies (fb563e8) (#​704 by @​renovate[bot])
• deps: Update all non-major dependencies (48a1e26) (#​694 by @​renovate[bot])
• deps: Update all non-major dependencies (a6eeff6)
• deps: Update all non-major dependencies (c74b327) (#​678 by @​renovate[bot])
• Update sapphire dependencies (a837459)
• deps: Update all non-major dependencies (43df709) (#​574 by @​renovate[bot])
• deps: Update all non-major dependencies (7909d16) (#​573 by @​renovate[bot])
• deps: Update all non-major dependencies (ee64834) (#​546 by @​renovate[bot])

🚀 Features

• Allow passing a custom instance of the logger (dc7c810) (#​739 by @​WeslleyNasRocha)
• logger: Add transports (c2464a5) (#​608 by @​UndiedGamer)

swc-project/swc (@​swc/core)

v1.13.2

Compare Source

Bug Fixes

• (es/minifier) Remove the last break in the second switch (#​10923) (3ed4a12)

• (es/parser) Reject malformed phase import statements (#​10912) (5fde348)

• (swc_core) Add default-features = false to drop stacker (#​10916) (38b45b7)

Features

• (es/compiler) Improve structure (#​10903) (0cc6743)

• (es/compiler) Merge private_in_object and static_blocks (#​10909) (c1405da)

• (es/compiler) Merge logical assignments (#​10914) (ccbfcd1)

• (es/compiler) Merge export_namespace_from (#​10917) (ba6cc71)

• (es/renamer) Add renamer_keep_contexts (#​10907) (1b15171)

Miscellaneous Tasks

• (claude) Use Opus and allow assigning to the claude-bot (3275b9c)

Performance

• (es/lexer) Remove option for handler (#​10881) (1ad8506)

• (es/lexer) Reduce memory move (#​10906) (145fba4)

• (es/lexer) Reduce context query (#​10910) (443aa1c)

• (es/lexer) Reduce query and comparison (#​10919) (400c996)

• (es/minifier) Make get_type for === lazy (#​10920) (4eab8e8)

• (es/minifier) Reduce get_type calls (#​10922) (9d55e88)

• (es/parser) Reduce check during parsing binding (#​10905) (92ca5ec)

• (es/parser) Reduce comparison (#​10911) (e00c178)

Refactor

• (es/compat) Initialize compiler API (#​10902) (d6566ee)

• (es/lexer) EOF Token (#​10880) (54c866a)

• (es/parser) Reduce input_mut() calls (#​10899) (1816368)

• (es/parser) Remove unnecessary PResult (#​10900) (27e548d)

• (es/preset-env) Apply swc_ecma_compiler in preset env (#​10921) (6f5b72a)

Testing

• (es/minifier) Update #​10918 test case (#​10924) (57fb106)

v1.13.1

Compare Source

Bug Fixes

• (es/compat) Properly handle rest assignment in for-in/of RHS (#​10883) (5d11851)

• (es/decorators) Handle empty class members (#​10892) (fe44972)

• (es/minifier) Hoist props when only props are used (#​10891) (452fc98)

• (es/minifier) Recursively check stmt for variable when inlining function (#​10896) (e37a93d)

• (es/minifier) Termination check when stmts containing switch (#​10898) (4429b20)

• (es/parser) Fix parsing of JSX identifiers (#​10894) (0047c39)

• (ts/fast-strip) Strip private method overloads (#​10886) (cdb6e87)

Testing

• (es/minify) Verify fixed issue (#​10888) (86c1dca)

v1.13.0

Compare Source

Bug Fixes

• (es/lexer) Disallow legacy octal literals as BigInt (#​10867) (430fbf4)

• (es/minifier) Restrict IIFE inlining in class contexts (#​10879) (a01b54a)

• (es/parser) Mark static as reserved in strict mode (#​10861) (5bdddd7)

Features

• (es/minifier) Drop unused rest paramters (#​10857) (5305486)

• (es/minifier) Enhance IIFE invoker for arrow functions (#​10860) (2b1ce3d)

• (plugin/runner) Use wasmer-wasix sys-minimal feature to reduce binary size (#​10638) (b5f704a)

Performance

• (es/lexer) Reduce comparison while reading numbers (#​10864) (c6ba5c2)

• (es/lexer) Remove unnecessary check when reading keywords (#​10866) (4aefe0e)

• (es/parser) Reduce comparisons (#​10862) (3bd9aad)

• (es/parser) Remove useless alloc (#​10865) (3ebf088)

• (es/parser) Reduce token query (#​10869) (d93ef64)

• (es/parser) Remove duplicate check (#​10872) (fe76460)

• (es/parser) Remove duplicate check (#​10874) (064123b)

• (swc_error_reporters) Avoid creating miette handler when no diagnostics (#​10852) (93b318f)

Refactor

• (es/lexer) Avoid passing convert (#​10868) (77393f8)

• (es/minifier) Cleanup (#​10882) (2595cb1)

• (es/parser) Remove duplicate check for reservedness (#​10850) (4897bfd)

• (es/parser) Remove span swap operation in parser (#​10854) (32f4bb8)

v1.12.14

Compare Source

Bug Fixes

• (es/minifier) Don't inline arrow when it contain this (#​10825) (8b43bb3)

• (es/parser) Make export in NS to not affect file type (#​10799) (ae22033)

• (es/parser) Correctly check ambient context (#​10802) (f97ea03)

Features

• (es/parser) Enable support for dynamic import with defer phase (#​10845) (097d29d)

• (plugin) Remove bytecheck to make Wasm plugins backward compatible (#​10842) (30ad808)

Miscellaneous Tasks

• (bindings) Fix dependency issues (7c57fbb)

• (deps) Update class-validator to avoid comments (#​10819) (bacfa4b)

• (ide) Enable --workspace for rust-analyzer check (#​10809) (92647ff)

Performance

• (es/minifier) Use u8 for remaining_depth (#​10833) (ed6956a)

• (hstr) Inline one more byte (#​10817) (3886c97)

• (hstr) Remove static tag (#​10832) (66ae1e8)

Refactor

• (es/helpers) Make inline helpers optional at compile time (#​10808) (53f3881)

• (es/lexer) Don't store buffer in lexer (#​10830) (cac40f1)

• (es/lints) Remove warnings without features (#​10794) (41d507f)

• (es/parser) Reduce token query (#​10834) (5cd5185)

• (es/parser) Reduce call to parse_decorators (#​10846) (356d3a0)

• (es/parser) Remove duplicate check (#​10847) (2b04efd)

• (es/preset-env) Use strpool,phf for corejs2 data (#​10803) (1652fd8)

• (es/react) Remove redundant replace calls (#​10795) (a670b37)

• (es/react) Remove count_children (#​10818) (2116ab2)

• (hstr) Cleanup duplicate header (#​10812) (630dde9)

• (hstr) Make the deallocation of Atoms explicit (#​10813) (406433d)

• (hstr) Remove is_global (#​10820) (afda0f9)

Testing

• (es/plugin) Test memory layout of archived types (#​10841) (502e991)

v1.12.11

Compare Source

Bug Fixes

• (ci) Fix CI (#​10790) ([b3f9760](h

---

Configuration

📅 Schedule: Branch creation - "before 6pm every weekday" in timezone Asia/Kolkata, Automerge - "after 9pm every weekday" in timezone Asia/Kolkata.

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.