chore(deps): update patch/minor dependencies #593

renovate · 2024-09-06T01:14:56Z

This PR contains the following updates:

Package	Change	Type	Update
@prisma/client (source)	`6.7.0` -> `6.11.1`	dependencies	minor
@sapphire/decorators (source)	`6.1.1` -> `6.2.0`	dependencies	minor
@sapphire/framework (source)	`5.3.4` -> `5.3.6`	dependencies	patch
@sapphire/plugin-logger (source)	`4.0.2` -> `4.1.0`	dependencies	minor
@skyra/env-utilities (source)	`2.0.0` -> `2.0.1`	dependencies	patch
@types/node (source)	`22.15.17` -> `22.16.3`	devDependencies	minor
@typescript-eslint/eslint-plugin (source)	`8.32.0` -> `8.36.0`	devDependencies	minor
@typescript-eslint/parser (source)	`8.32.0` -> `8.36.0`	devDependencies	minor
@vitest/coverage-v8 (source)	`3.1.3` -> `3.2.4`	devDependencies	minor
discord.js (source)	`14.19.3` -> `14.21.0`	dependencies	minor
libpg-query	`16.3.0` -> `16.5.5`	devDependencies	minor
node (source)	`22.14.0` -> `22.17.0`	volta	minor
prettier (source)	`3.5.3` -> `3.6.2`	devDependencies	minor
prisma (source)	`6.7.0` -> `6.11.1`	devDependencies	minor
re2	`1.21.4` -> `1.22.1`	dependencies	minor
vitest (source)	`3.1.3` -> `3.2.4`	devDependencies	minor
yarn (source)	`4.8.1` -> `4.9.2`	packageManager	minor
yarn (source)	`4.8.1` -> `4.9.2`	volta	minor

Release Notes

prisma/prisma (@prisma/client)

`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:

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 @&#8203;default(uuid())
  region String @&#8203;shardKey
}

// Multi-column shard key
model User {
  id         String @&#8203;default(uuid())
  country    String
  customerId String
  @&#8203;@&#8203;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 @&#8203;prisma/adapter-pg

Once installed, you can instantiate PrismaClient as follows:

import { PrismaClient } from './generated/prisma'
import { PrismaPg } from '@&#8203;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!

`v6.8.2`

Compare Source

Today, we are issuing the 6.8.2 patch release. It fully resolves an issue with the prisma init and prisma dev commands for some Windows users who were still facing problems after the previous incomplete fix in version 6.8.1.

Fixes:

https://github.com/prisma/prisma/issues/27195

`v6.8.1`

Compare Source

Today, we are issuing the 6.8.1 patch release. It fixes an issue with the prisma init and prisma dev commands on Windows.

Fixes

https://github.com/prisma/prisma/issues/27192

`v6.8.0`

Compare Source

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

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

Highlights

Local development with Prisma Postgres via `prisma dev` (Early Access)

In this release, we're releasing a way to develop against Prisma Postgres locally — no Docker required!

To get started, run the new prisma dev command:

npx prisma dev # starts a local Prisma Postgres server

This command spins up a local Prisma Postgres instance and prints the connection URL that you'll need to set as the url of your datasource block to point to a local Prisma Postgres instance. It looks similar to this:

datasource db {
  provider = "postgresql"
  url      = "prisma+postgres://localhost:51213/?api_key=ey..." 
}

You can then run migrations and execute queries against this local Prisma Postgres instance as with any remote one. Note that you need to keep the prisma dev process running in order to interact with the local Prisma Postgres instance.

📚 Learn more in the docs.

Native Deno support in `prisma-client` generator (Preview)

In this release, we're removing the deno Preview feature from the prisma-client-js generator. If you want to use Prisma ORM with Deno, you can now do so with the new prisma-client generator:

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

📚 Learn more in the docs.

VS Code Agent Mode: AI support with your database workflows

Have you tried agent mode in VS Code already?

"The agent acts as an autonomous pair programmer that performs multi-step coding tasks at your command, such as analyzing your codebase, proposing file edits, and running terminal commands."

As of this release, your agent is capable of supporting you with your database workflows more than ever! If you're using VS Code and have the Prisma VS Code extension installed, your agent now is able to help you with your database workflows, such as:

checking the status of your migrations (e.g. telling you if migrations haven't been applied)
creating and running schema migrations for you
authenticating you with the Prisma Console
provisioning new Prisma Postgres instances so you can start coding right away

All you need to do is make sure you're using the latest version of Prisma's VS Code extension and your agent is ready to go 🚀

📚 Learn more in the docs.

Other news

You voted, we acted: New Singapore region for Prisma Postgres

We recently ran a poll where we asked you which region you'd like to see next for Prisma Postgres. The majority vote went to Asia Pacific (Singapore), so as of today, you're able to spin up new Prisma Postgres instances in the ap-southeast-1 region.

We're not stopping here — keep an eye out on X for another poll asking for your favorite regions that we should add!

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)

`v5.3.5`

Compare Source

🐛 Bug Fixes

Update sapphire dependencies (a04f44a)
deps: Update all non-major dependencies (e99277a) (#837 by @renovate[bot])

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)

skyra-project/archid-components (@skyra/env-utilities)

`v2.0.1`

Compare Source

🐛 Bug Fixes

env-utilities: Bump dotenv dependencies (2a3e19d)

typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

`v8.36.0`

Compare Source

This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

`v8.35.1`

Compare Source

🩹 Fixes

remove prettier from eslint-plugin (#11339)

❤️ Thank You

Abhijeet Singh @cseas

You can read about our versioning strategy and releases on our website.

`v8.35.0`

Compare Source

🚀 Features

eslint-plugin: [no-base-to-string] add checkUnknown Option (#11128)

❤️ Thank You

Kim Sang Du @developer-bandi

You can read about our versioning strategy and releases on our website.

`v8.34.1`

Compare Source

This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

`v8.34.0`

Compare Source

🩹 Fixes

typescript-estree: add validation to interface extends (#11271)

❤️ Thank You

Tao

You can read about our versioning strategy and releases on our website.

`v8.33.1`

Compare Source

🩹 Fixes

exclude docs/ directory from eslint-plugin package (#11251)

❤️ Thank You

roottool

You can read about our versioning strategy and releases on our website.

`v8.33.0`

Compare Source

This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

`v8.32.1`

Compare Source

🩹 Fixes

eslint-plugin: [consistent-indexed-object-style] check for indirect circular types in aliased mapped types (#11177)
eslint-plugin: [consistent-indexed-object-style] adjust auto-fixer to generate valid syntax for TSMappedType with no type annotation (#11180)
eslint-plugin: [no-deprecated] support computed member access (#10867)
eslint-plugin: [no-unnecessary-type-conversion] shouldn't have fixable property (#11194)

❤️ Thank You

Azat S. @azat-io
Dima Barabash @dbarabashh
Ronen Amiel

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@typescript-eslint/parser)