fix(deps): update all non-major dependencies #95
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.6.0
->6.7.0
6.6.0
->6.7.0
22.15.2
->22.15.3
22.15.17
(+13)22.14.0-bookworm-slim
->22.15.0-bookworm-slim
7.4.2-bookworm
->7.4.3-bookworm
9.25.1
->9.26.0
6.6.0
->6.7.0
4.19.3
->4.19.4
8.31.0
->8.31.1
8.32.0
Release Notes
prisma/prisma (@prisma/client)
v6.7.0
Compare Source
Today, we are excited to share the
6.7.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 (Early Access)
If you're a regular visitor of our company blog, you may already know that we're currently working on moving the core of Prisma from Rust to TypeScript. We have written extensively about why we're moving away from Rust and already shared the first measurements of performance boosts we saw from the re-write.
This re-write is not just a move from one programming language to another. It fundamentally improves the architecture of Prisma ORM and replaces the Query Engine (which is written in Rust and deployed as a standalone binary) with a much leaner and more efficient approach that we call Query Compiler.
In this release, we're excited to give you Early Access to the new Query Compiler for PostgreSQL and SQLite database 🥳 Support for more database will follow very soon!
To use the new "Rust-free" version of Prisma ORM, add the
queryCompiler
(new) anddriverAdapters
feature flags to your client generator:Now run
prisma generate
to re-generate Prisma Client. If you didn't use a driver adapter before, you'll need to install one. For example, the one for PostgreSQL:Once installed, you can instantiate
PrismaClient
as follows:This version of
PrismaClient
doesn't have a Query Engine binary and you can use it in the exact same way as before.📚 Learn more in the docs.
Support for
better-sqlite3
JavaScript driver (Preview)Driver adapters are Prisma ORM's way of letting you use JS-native drivers (like
pg
) to interact with your database. In this release, we're introducing a new driver adapter for using thebetter-sqlite3
package, so you can now interact with SQLite database in a JS-native way.To use it, first enable the
driverAdapters
Preview feature flag in on your clientgenerator
, then install these libraries:Now you can instantiate Prisma Client as follows:
📚 Learn more in the docs.
Multi-file Prisma schemas are now production-ready
The
prismaSchemaFolder
Preview feature is moving into General Availability 🎉 With that change, Prisma ORM now by default supports splitting your Prisma schema file and e.g. lets you organize your schema as follows:prisma/schema.prisma
→ defines data source and generatorprisma/models/posts.prisma
→ definesPost
modelprisma/models/users.prisma
→ definesUser
modelprismaSchemaFolder
Preview feature in the last 6.6.0 release. If you've been using this feature to split your Prisma schema, make sure to read the release notes and update your project accordingly.📚 Learn more in the docs.
Splitting generated output with new
prisma-client
generator (Preview)With the
prisma-client-js
generator, the generated Prisma Client library is put into a singleindex.d.ts
file. This sometimes led to issues with large schemas where the size of the generated output could slow down code editors and breaking auto-complete.As of this release, our new
prisma-client
generator (that was released in 6.6.0) now splits the generated Prisma Client library into multiple files and thus avoids the problems of a single, large output file.Also: As a bonus, we now ensure that generated files do not raise any ESLint and TypeScript errors!
Before
After
📚 Learn more in the docs.
Company news
Our team has been busy shipping more than just the ORM! Check out these articles to learn what else we've been up to recently:
eslint/eslint (eslint)
v9.26.0
Compare Source
privatenumber/tsx (tsx)
v4.19.4
Compare Source
typescript-eslint/typescript-eslint (typescript-eslint)
v8.31.1
Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
Configuration
📅 Schedule: Branch creation - "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.
This PR was generated by Mend Renovate. View the repository job log.