fix(deps): update all non-major dependencies #339
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:
5.9.1
->5.10.1
5.9.1
->5.10.1
7.6.16
->7.6.17
7.6.16
->7.6.17
7.6.16
->7.6.17
7.6.16
->7.6.17
7.6.16
->7.6.17
7.6.16
->7.6.17
7.6.16
->7.6.17
7.6.16
->7.6.17
1.2.1
->1.2.2
16.4.4
->16.4.5
2.4.3
->2.5.0
5.0.5
->5.0.6
5.9.1
->5.10.1
7.6.16
->7.6.17
Release Notes
prisma/prisma (@prisma/adapter-neon)
v5.10.1
Compare Source
Today, we are issuing the
5.10.1
patch release.Fix in Prisma Client / Prisma CLI
v5.10.0
Compare Source
Today, we are excited to share the
5.10.0
stable release 🎉🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.
Highlights
Optimized relation queries in MySQL (Preview)
This release brings the optimizations for relation queries from the previous releases to MySQL as well! This means that by enabling the
relationJoins
Preview feature with themysql
database provider, you now also get access to therelationLoadStrategy
option in relation queries that let you choose whether you want to merged relations on the application- or database-level.If you enable the
relationJoins
Preview feature, you can choose between thejoin
andquery
options:join
(default): Sends a single query to the database and joins the data on the database-level.query
: Sends multiple queries to the database and joins the data on the application-level.To get started, enable the Preview feature in your Prisma schema:
Be sure to re-generate Prisma Client afterwards:
And finally, specify the relation loading strategy for your relation query via the
relationLoadStrategy
option as follows:Note that in the example above, the
relationLoadStrategy
could be omitted altogether becausejoin
is used as the default value.A few notes about
relationLoadStrategy
support on MySQL:relationLoadStrategy
is supported for MySQL v8.0.14 and higher. MariaDB is not supported.LATERAL
JOINs which are used on PostgreSQL).Configure transaction options in the
PrismaClient
constructorThis feature enables you to configure the following transaction options on a global level via the
PrismaClient
constructor:isolationLevel
: Sets the transaction isolation level. By default, this is set to the value currently configured in your database.timeout
: The maximum amount of time the interactive transaction can run before being canceled and rolled back. The default value is 5 seconds.maxWait
: The maximum amount of time Prisma Client will wait to acquire a transaction from the database. The default value is 2 seconds.Here is an example of how you can set this value globally for all transactions:
Thanks a lot to our fantastic community member
@tockn
, who took the initiative to implement this feature in Prisma ORM 🎉Note that you can still override the global values by setting them on a particular transaction.
New
P2037
code for “Too many database connections opened” errorsWe introduced a new error code for “Too many database connections opened” errors:
P2037
. You can find all error codes in our documentation.Access the Prisma Data Platform via Prisma CLI
Now available in Early Access, you can manage your workspace and configure Prisma Accelerate and Prisma Pulse directly from the terminal.
Visit our docs to learn more about the integration and try it out for yourself!
Fixes and improvements
Prisma Client
Option::unwrap()
on aNone
value when using the relationJoins preview feature with driver adaptersPrisma.TransactionClient
appears to be missing types@prisma/client
in Next.js middleware$extends
always returnany
Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.
t3.bookGenreTitle
does not exist in the current database"relationJoins
preview feature: calledOption::unwrap()
on aNone
valuestorybookjs/storybook (@storybook/addon-a11y)
v7.6.17
Compare Source
storybookjs/storybook (@storybook/addon-essentials)
v7.6.17
Compare Source
storybookjs/storybook (@storybook/addon-interactions)
v7.6.17
Compare Source
vercel/analytics (@vercel/analytics)
v1.2.2
Compare Source
What's Changed
Full Changelog: vercel/analytics@1.2.1...1.2.2
motdotla/dotenv (dotenv)
v16.4.5
Compare Source
Changed
path
option. return to historical behavior: do not attempt to auto find.env
ifpath
set. (regression was introduced in16.4.3
) #814i18next/i18next-http-backend (i18next-http-backend)
v2.5.0
Compare Source
ai/nanoid (nanoid)
v5.0.6
Compare Source
storybookjs/storybook (storybook)
v7.6.17
Compare Source
Configuration
📅 Schedule: Branch creation - "before 4am on Monday,before 4am on Thursday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.