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:
2.0.1
->2.2.0
5.4.0
->5.11.0
0.22.32
->0.22.35
29.5.5
->29.5.12
18.18.3
->18.19.24
0.37.59
->0.37.74
14.13.0
->14.14.1
16.3.1
->16.4.5
3.0.1
->3.1.0
5.4.0
->5.11.0
29.1.1
->29.1.2
10.9.1
->10.9.2
5.2.2
->5.4.2
Release Notes
discordjs/discord.js (@discordjs/rest)
v2.2.0
Compare Source
Bug Fixes
Features
Typings
v2.1.0
Compare Source
Bug Fixes
Documentation
Features
prisma/prisma (@prisma/client)
v5.11.0
Compare Source
Today, we are excited to share the
5.11.0
stable release 🎉🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.
Highlights
Edge function support for Cloudflare and Vercel (Preview)
We’re thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview 🥳 As of this release, you can deploy your apps that are using Prisma ORM to:
In order to deploy to an edge function, you’ll need to use a compatible database driver (along with its Prisma driver adapter):
pg
driver (for traditional PostgreSQL databases)@libsql/client
driver (for SQLite databases hosted via Turso)Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.
Performance improvements in nested
create
operationsWith Prisma ORM, you can create multiple new records in nested queries, for example:
In previous versions, Prisma ORM would translate this into multiple SQL
INSERT
queries, each requiring its own roundtrip to the database. As of this release, these nestedcreate
queries are optimized and theINSERT
queries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.With this change, using the nested
create
option to create multiple records effectively becomes equivalent to using a nestedcreateMany
operation (except thatcreateMany
only works with one-to-many relations, whereascreate
works both with one-to-many and many-to-many).Fixes and improvements
Prisma Client
console.log(new PrismaClient())
enum
throws error (collationcp1250_czech_cs
or similar)NOT
condition leaks out of its desired boundsPrismaClient
object is slowprisma generate
on Litespeed Web Server cPanel with sshtsc
:Cannot find namespace 'debug'.
push
method still unimplemented for scalar lists in CockroachDBInvalid character
error persists on 5.10.1 in Prisma StudioruntimeDescription
is not defined errorPrisma Migrate
npx prisma db pull
with DeepinOS 20.9GNU/LInuxLinux Mint
Error: Invalid character
whenschema.prisma
includes Chinese/Non-ASCII characters in a commentPrisma Engines
v5.10.2
Compare Source
Today, we are issuing the
5.10.2
patch release.Fix in Prisma CLI
Invalid character
error persists on 5.10.1 in Prisma Studiov5.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
valuev5.9.1
Compare Source
Today, we are issuing the
5.9.1
patch release.Fixes in Prisma Client
In
5.9.0
we have changed our conditional exports in@prisma/client
. This resulted in broken types for TypesScript users using certain combinations ofmodule
/moduleResolution
settings. Additionally, it also caused a regression for Next.js users which have encountered invalid error messages from our side.You can now try out
5.9.1
and let us know if you find a bug at https://pris.ly/prisma-prisma-bug-reportError: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.
#22889Note: many issues are duplicates.
v5.9.0
Compare Source
Today, we are excited to share the
5.9.0
stable release 🎉🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.
This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks:
Highlights
Optimized result sets for more efficient queries
We continue our efforts of the performance of Prisma Client queries. In
5.1.0
, we introduced theRETURNING
keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use ofRETURNING
to SQLite and a broader range of queries for existing databases (e.g.delete
on PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs:SQL Server: Return proper error for unreachable database
When trying migrate/introspect a SQL server instance that’s unreachable, Prisma ORM now returns the correct
P1001
error instead of failing without an error. Learn more in this PR: SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url.Fixes and improvements
Prisma Client
select
queries on create/update/deletePrisma Migrate
ERROR: column "..." being dropped, try again later
when applying migrations with CRDB 23.1Language tools (e.g. VS Code)
Company news
Test edge functions support in Early Access
Today, the only way how to use Prisma ORM in edge functions (e.g. Cloudflare Workers or Vercel Edge Functions) is by using Prisma Accelerate. However, we are actively working on making Prisma ORM compatible with edge functions natively as well. If you want to become an early tester, you can apply for the private Early Accessing program by taking this survey.
We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing
Last year, AWS announced the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on IPv6. Learn more in this technical deep dive into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate.
Credits
Huge thanks to @laplab, @Druue, @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @almeidx, @victorgdb, @tinola, @sampolahtinen, @AikoRamalho, @petradonka for helping!
v5.8.1
Compare Source
Today, we are issuing the
5.8.1
patch release.Fix in Prisma Client
v5.8.0
Compare Source
🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release. 🌟
Highlights
Happy New Year from your friends at Prisma! 🎊
In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉
relationJoins
improvements: Relation loading strategy per query (Preview)In version 5.7.0, we released
relationJoins
into Preview. TherelationJoins
feature enables support forJOIN
s for relation queries.This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case.
You can now load relation data using either of the following strategies:
join
— usesJOIN
s to fetch relation dataquery
— uses sub-queries to fetch relation dataWhen the
relationJoins
Preview feature is enabled, by default, the relation fetching strategy used isjoin
. You can override the default behavior by using therelationLoadStrategy
query option.To get started, enable the Preview feature:
… and specify the relation loading strategy for your query as follows:
Try it out and share your feedback and create a bug report if you encounter any issues.
Survey: Edge functions support
We’re working on bringing Edge function support to Prisma ORM and we would appreciate your input by submitting a response to our survey. By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out.
Fixes and improvements
Prisma Client
target
andtimestamp
are undefined ininfo
events in Data Proxy clienttimestamp
andduration
in query events with Data Proxycitext
fields with neon database driver causes conversion errorPrisma Migrate
Environment is non-interactive
whenVERCEL
env var is definedLanguage tools (e.g. VS Code)
Error validating field 'id' in model 'Post': MongoDB '@​default(auto())' fields must have 'ObjectId' native type.
Credits
Huge thanks to @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @fqazi, @KhooHaoYit, @alencardc, @Oreilles, @tinola, @AikoRamalho, @luxaritas for helping!
Company news
🎉 A billion queries and counting: Prisma Accelerate
Prisma Accelerate, our global database cache has served over 1 billion queries since its General Availability launch.
We’d like to give a shoutout to our team and everyone who’s been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024!
🔮 Prisma ORM Ecosystem
Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? Let us know.
We would like to learn about it and feature it on our Ecosystem page.
💼 We’re hiring
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. Check out our Careers page for open positions.
v5.7.1
Compare Source
Today, we are issuing the
5.7.1
patch release.This patch fixes multiple small problems in our
relationJoins
preview feature. If you ran into problems when testingrelationJoins
before, please give it another go with 5.7.1 and share your feedback or create a bug report if you encounter any issues.Fixes in Prisma Client
relationJoins
: Int[] return as nullrelationJoins
: fails when filtering includes by isNot: nullrelationJoins
: "The table (not available) does not exist in the current database."relationJoins
: PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }relationJoins
: Inconsistent column data: Unexpected conversion failure from String to datetime. Reason: $trailing inputv5.7.0
Compare Source
🌟 Help us spread the word about Prisma by starring the repo or posting on X (formerly Twitter) about the release.
Highlights
✨ In this release, we improved the SQL queries Prisma Client generates for you with two new Preview features, the driver adapters, and support for the database drivers we currently support. 5.7.0 will be the last release of the year. Stay tuned for the next one in January! ✨
Preview support for
JOIN
s for relation queries for PostgreSQL and CockroachDBWe’re excited to announce Preview support for
JOIN
s in Prisma Client when querying relations. Support forJOIN
s has been a long-standing feature request, and this release adds support for PostgreSQL and CockroachDB. The upcoming releases will expand support for other databases Prisma supports.To get started using
JOIN
s, enable the Preview feature in your Prisma schema:Run
prisma generate
to regenerate Prisma Client and enable the Preview feature.Prisma Client will use a
JOIN
in your query to fetch relation data for a majority of the cases.Example queries
1-1 relation queries example
Prisma Client query
SQL
1-m relation queries example
Prisma Client query
SQL
m-n relation queries example
Prisma Client query
SQL
Share your feedback and create a bug report if you encounter any issues.
Prisma’s
distinct
option now uses SQL queries (Preview)From this release, Prisma Client’s
distinct
option now uses the native SQLDISTINCT ON
for unordered queries with PostgreSQL and CockroachDB. The upcoming releases will expand support for the other databases that Prisma supports.Prisma Client already supports querying for distinct records. However, Prisma Client took care of the post-processing for distinct records in memory.
To get started, enable the Preview feature in your Prisma schema:
Regenerate your Prisma Client to get started using the Preview feature.
Given the following Prisma Client query:
Before 5.7.0
Previously, Prisma Client handled the post-processing to select distinct records in-memory. Therefore, the following query was generated and executed against your database:
After 5.7.0
Share your feedback and create a bug report if you encounter any issues.
Improved support for Netlify using Node.js v20
In this release, we improved Prisma support when deploying to Netlify on Node.js v20. Previously, the Prisma Client could not resolve the location of the Query Engine after deploying to Netlify when using Node.js v20. If you run into this issue, we recommend updating to Prisma v5.7.0.
We recommend giving this comment on GitHub a read if you are not yet able to upgrade Prisma, to learn how to get around the error.
Fixes and improvements
Prisma Client
InterpretationError("Unable to convert expression result into a set of selection results", None)
(starting with 5.2.0)TRUNCATE
ing the table on CockroachDB:placeholder $1 already has type string, cannot assign Color
Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x"
)Prisma
Prisma Migrate
prisma debug
command does not show env variables declared in.env
fileCredits
Huge thanks to @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @fqazi, @KhooHaoYit, @alencardc, @Oreilles, @christianledgard, @skyzh, @alula, @AikoRamalho, @petradonka for helping!
Company news
💼 We’re hiring!
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.
We're hiring for the following roles:
v5.6.0
Compare Source
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Driver adapters improvements (Preview)
In version 5.4.0, we released
driverAdapters
into Preview. ThedriverAdapters
feature enables Prisma Client to access your database using JavaScript or Serverless database drivers.In this release, we fixed many bugs for the existing driver adapters. We appreciate all the community feedback that has helped us improve this feature!
PlanetScale serverless driver adapter improvements
This release also introduces a small breaking change to the
@prisma/adapter-planetscale
package to improve its stability and performance. The serverless driver adapter will now use a connection pool instead of a single connection from PlanetScale’s serverless driver.In case you’re using the
@prisma/adapter-planetscale
, update your Prisma Client instance with the following:Request for feedback
We encourage you to try out the driver adapters and share your feedback to help us move it to General Availability in either of the following GitHub discussions:
Refer to our docs to learn more about driver adapters.
New
prisma debug
commandThis release introduces a new command:
prisma debug
. The command provides debugging information such as environment variables that Prisma Client, Prisma Migrate, Prisma CLI, and Prisma Studio use. The command is also useful when creating a bug report as the information complements the output of theprisma -v
command.You can learn more about the command in our docs.
Read replicas extension improvements
We also released version 0.3.0 of the
@prisma/extension-read-replicas
package that contains the following improvements:A new
$replica()
method that explicitly enables you to use a replica for your query.For example, by default, the
queryRaw
andexecuteRaw
methods are forwarded to the primary database, as they could try to write to the database. You can use the$replica()
method with either of the*Raw
methods to explicitly execute your query against a replica instead of your primary database.Validation for when there’s an empty list of replicas.
Webpack bundling fixes
We want to thank you, our community members, for your contributions! 🙏
You can find additional information on the changes in the extension’s release. You can learn more about the extension in the announcement blog post.
Package provenance
npm has introduced provenance statements to improve supply-chain security and transparency of packages. This allows developers to verify where and how packages are built.
Starting with the 5.6.0 release, all npm packages for Prisma ORM will be published with provenance statements. If you maintain a Prisma Client extension or generator, we encourage you to enable provenance statements when publishing to npm.
Fixes and improvements
Prisma Migrate
db push
with invalid connection string: Connection string redacted, weird grammardb pull --url=...
logs full connection string onP4001 The introspected database was empty
Prisma Client
prisma_pool_connections_idle
reports misleading number@prisma/adapter-planetscale
PrismaPlanetScale
adapter to the constructorError: sha256 checksum of https://binaries.prisma.sh/all_commits/475c616176945d72f4330c92801f0c5e6398dc0f/windows/query_en gine.dll.node.gz (zipped) should be 748d039badd0919d022fff7d554b66b6937b79035861a6ae9a80c5a95eee76f5 but is b867ad335ee6f58c6a38f665dd641c95e6adff3061f92b7613c62cae1c3362bb
Prisma CLI
prisma debug
Credits
Huge thanks to @onichandame, @LucianBuzzo, @RobertCraigie, @fqazi, @KhooHaoYit, @alencardc, @Oreilles, @christianledgard, @skyzh, @alula, @luxaritas, @Nasfame, @lukahartwig, @steebchen, @icanipa for helping!
Miscellaneous
Prisma Accelerate is now Generally Available
We're excited to share that Prisma Accelerate is now Generally Available. Prisma Accelerate is a global database cache that's available in over 280 locations and provides scalable connection pooling for serverless and edge applications.
Learn more in the announcement blog post. Sign up and try out Prisma Accelerate
💼 We’re hiring!
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.
We're hiring for an Engineering Manager: Prisma Data Platform.
v5.5.2
Compare Source
Today, we are issuing the
5.5.2
patch release.Fix in Prisma CLI
[
v5.5.1
](https://togithub.com/prisma/prismaConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.