prisma/prisma (@prisma/client)
### [`v5.9.1`](https://togithub.com/prisma/prisma/releases/tag/5.9.1)
[Compare Source](https://togithub.com/prisma/prisma/compare/5.9.0...5.9.1)
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 of `module`/`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-report
- [\[5.9.0\] Getting strange types after generating #22903](https://togithub.com/prisma/prisma/issues/22903)
- [v5.9.0 / Don't generate type. And the error from the previous version is still there #22896](https://togithub.com/prisma/prisma/issues/22896)
- [\[5.9.0\] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #22893](https://togithub.com/prisma/prisma/issues/22893)
- [`Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.` #22889](https://togithub.com/prisma/prisma/issues/22889)
- [\[5.9.0\] All queries result in any type #22888](https://togithub.com/prisma/prisma/issues/22888)
- [Prisma edge runtime error #22886](https://togithub.com/prisma/prisma/issues/22886)
- [please how i cant fix this message issues #22885](https://togithub.com/prisma/prisma/issues/22885)
- [\[v5.9.0\] $extends always return any #22884](https://togithub.com/prisma/prisma/issues/22884)
- [\[5.9.0\] @prisma/client in Next.js middleware #22877](https://togithub.com/prisma/prisma/issues/22877)
- [Error after Upgrading from 5.8.1 to 5.9.0 #22875](https://togithub.com/prisma/prisma/issues/22875)
- [\[5.9.0 Bug\] Prisma.TransactionClient appears to be missing types #22870](https://togithub.com/prisma/prisma/issues/22870)
Note: many issues are duplicates.
### [`v5.9.0`](https://togithub.com/prisma/prisma/releases/tag/5.9.0)
[Compare Source](https://togithub.com/prisma/prisma/compare/5.8.1...5.9.0)
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](https://twitter.com/intent/tweet?text=Check) 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:
- Improve the performance of relation queries by introducing JOINs (see [last release](https://togithub.com/prisma/prisma/releases/tag/5.8.0)).
- Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our [survey](https://pris.ly/survey/edge-functions-release-notes-5-9-0)).
##### Highlights
##### Optimized result sets for more efficient queries
We continue our efforts of the performance of Prisma Client queries. In [`5.1.0`](https://togithub.com/prisma/prisma/releases/tag/5.1.0), we introduced the `RETURNING` keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of `RETURNING` 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:
- [feat(qe): avoid extra select on delete queries](https://togithub.com/prisma/prisma-engines/pull/4595)
- [feat(qe): enable queries with returning for sqlite](https://togithub.com/prisma/prisma-engines/pull/46)
##### 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](https://togithub.com/prisma/prisma/issues/11407).
##### Fixes and improvements
##### Prisma Client
- [Skip unnecessary `select` queries on create/update/delete](https://togithub.com/prisma/prisma/issues/8069)
- [.prisma/client: Name can't start with a dot](https://togithub.com/prisma/prisma/issues/17685)
- [Nested json is transformed to string when used “$type” key in object](https://togithub.com/prisma/prisma/issues/21454)
- [Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit](https://togithub.com/prisma/prisma/issues/22610)
##### Prisma Migrate
- [SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url](https://togithub.com/prisma/prisma/issues/11407)
- [Prisma errors fetching table 'CHECK_CONSTRAINTS' (which only exists in MySQL 8.0.16+) in MySQL 8.0.14](https://togithub.com/prisma/prisma/issues/19775)
- [`ERROR: column "..." being dropped, try again later` when applying migrations with CRDB 23.1](https://togithub.com/prisma/prisma/issues/20851)
##### Language tools (e.g. VS Code)
- [Extension wrongfully suggests Json as a valid type completion on Sqlite](https://togithub.com/prisma/language-tools/issues/1638)
##### 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](https://www.prisma.io/data-platform/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](https://pris.ly/survey/edge-functions-release-notes-5-9-0).
##### 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](https://www.prisma.io/blog/accelerate-ipv6-first) into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate.
##### Credits
Huge thanks to [@laplab](https://togithub.com/laplab), [@Druue](https://togithub.com/Druue), [@anuraaga](https://togithub.com/anuraaga), [@onichandame](https://togithub.com/onichandame), [@LucianBuzzo](https://togithub.com/LucianBuzzo), [@RobertCraigie](https://togithub.com/RobertCraigie), [@almeidx](https://togithub.com/almeidx), [@victorgdb](https://togithub.com/victorgdb), [@tinola](https://togithub.com/tinola), [@sampolahtinen](https://togithub.com/sampolahtinen), [@AikoRamalho](https://togithub.com/AikoRamalho), [@petradonka](https://togithub.com/petradonka) for helping!
Automattic/mongoose (mongoose)
### [`v8.1.2`](https://togithub.com/Automattic/mongoose/blob/HEAD/CHANGELOG.md#812--2024-02-08)
[Compare Source](https://togithub.com/Automattic/mongoose/compare/8.1.1...8.1.2)
\==================
- fix: include virtuals in document array toString() output if toObject.virtuals set [#14335](https://togithub.com/Automattic/mongoose/issues/14335) [#14315](https://togithub.com/Automattic/mongoose/issues/14315)
- fix(document): handle setting nested path to spread doc with extra properties [#14287](https://togithub.com/Automattic/mongoose/issues/14287) [#14269](https://togithub.com/Automattic/mongoose/issues/14269)
- fix(populate): call setter on virtual populated path with populated doc instead of undefined [#14314](https://togithub.com/Automattic/mongoose/issues/14314)
- fix(QueryCursor): remove callback parameter of AggregationCursor and QueryCursor [#14299](https://togithub.com/Automattic/mongoose/issues/14299) [DevooKim](https://togithub.com/DevooKim)
- types: add typescript support for arbitrary fields for the options parameter of Model functions which are of type MongooseQueryOptions [#14342](https://togithub.com/Automattic/mongoose/issues/14342) [#14341](https://togithub.com/Automattic/mongoose/issues/14341) [FaizBShah](https://togithub.com/FaizBShah)
- types(model): correct return type for findOneAndUpdate with includeResultMetadata and lean set [#14336](https://togithub.com/Automattic/mongoose/issues/14336) [#14303](https://togithub.com/Automattic/mongoose/issues/14303)
- types(connection): add type definition for `createCollections()` [#14295](https://togithub.com/Automattic/mongoose/issues/14295) [#14279](https://togithub.com/Automattic/mongoose/issues/14279)
- docs(timestamps): clarify that replaceOne() and findOneAndReplace() overwrite timestamps [#14337](https://togithub.com/Automattic/mongoose/issues/14337) [#14309](https://togithub.com/Automattic/mongoose/issues/14309)
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - "after 9am and before 5pm Monday" (UTC).
🚦 Automerge: Enabled.
♻ 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.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
5.8.1->5.9.129.5.11->29.5.1220.11.7->20.11.178.1.1->8.1.25.8.1->5.9.1Release Notes
prisma/prisma (@prisma/client)
### [`v5.9.1`](https://togithub.com/prisma/prisma/releases/tag/5.9.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.9.0...5.9.1) 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 of `module`/`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-report - [\[5.9.0\] Getting strange types after generating #22903](https://togithub.com/prisma/prisma/issues/22903) - [v5.9.0 / Don't generate type. And the error from the previous version is still there #22896](https://togithub.com/prisma/prisma/issues/22896) - [\[5.9.0\] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #22893](https://togithub.com/prisma/prisma/issues/22893) - [`Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.` #22889](https://togithub.com/prisma/prisma/issues/22889) - [\[5.9.0\] All queries result in any type #22888](https://togithub.com/prisma/prisma/issues/22888) - [Prisma edge runtime error #22886](https://togithub.com/prisma/prisma/issues/22886) - [please how i cant fix this message issues #22885](https://togithub.com/prisma/prisma/issues/22885) - [\[v5.9.0\] $extends always return any #22884](https://togithub.com/prisma/prisma/issues/22884) - [\[5.9.0\] @prisma/client in Next.js middleware #22877](https://togithub.com/prisma/prisma/issues/22877) - [Error after Upgrading from 5.8.1 to 5.9.0 #22875](https://togithub.com/prisma/prisma/issues/22875) - [\[5.9.0 Bug\] Prisma.TransactionClient appears to be missing types #22870](https://togithub.com/prisma/prisma/issues/22870) Note: many issues are duplicates. ### [`v5.9.0`](https://togithub.com/prisma/prisma/releases/tag/5.9.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.8.1...5.9.0) 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](https://twitter.com/intent/tweet?text=Check) 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: - Improve the performance of relation queries by introducing JOINs (see [last release](https://togithub.com/prisma/prisma/releases/tag/5.8.0)). - Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our [survey](https://pris.ly/survey/edge-functions-release-notes-5-9-0)). ##### Highlights ##### Optimized result sets for more efficient queries We continue our efforts of the performance of Prisma Client queries. In [`5.1.0`](https://togithub.com/prisma/prisma/releases/tag/5.1.0), we introduced the `RETURNING` keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of `RETURNING` 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: - [feat(qe): avoid extra select on delete queries](https://togithub.com/prisma/prisma-engines/pull/4595) - [feat(qe): enable queries with returning for sqlite](https://togithub.com/prisma/prisma-engines/pull/46) ##### 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](https://togithub.com/prisma/prisma/issues/11407). ##### Fixes and improvements ##### Prisma Client - [Skip unnecessary `select` queries on create/update/delete](https://togithub.com/prisma/prisma/issues/8069) - [.prisma/client: Name can't start with a dot](https://togithub.com/prisma/prisma/issues/17685) - [Nested json is transformed to string when used “$type” key in object](https://togithub.com/prisma/prisma/issues/21454) - [Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit](https://togithub.com/prisma/prisma/issues/22610) ##### Prisma Migrate - [SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url](https://togithub.com/prisma/prisma/issues/11407) - [Prisma errors fetching table 'CHECK_CONSTRAINTS' (which only exists in MySQL 8.0.16+) in MySQL 8.0.14](https://togithub.com/prisma/prisma/issues/19775) - [`ERROR: column "..." being dropped, try again later` when applying migrations with CRDB 23.1](https://togithub.com/prisma/prisma/issues/20851) ##### Language tools (e.g. VS Code) - [Extension wrongfully suggests Json as a valid type completion on Sqlite](https://togithub.com/prisma/language-tools/issues/1638) ##### 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](https://www.prisma.io/data-platform/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](https://pris.ly/survey/edge-functions-release-notes-5-9-0). ##### 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](https://www.prisma.io/blog/accelerate-ipv6-first) into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate. ##### Credits Huge thanks to [@laplab](https://togithub.com/laplab), [@Druue](https://togithub.com/Druue), [@anuraaga](https://togithub.com/anuraaga), [@onichandame](https://togithub.com/onichandame), [@LucianBuzzo](https://togithub.com/LucianBuzzo), [@RobertCraigie](https://togithub.com/RobertCraigie), [@almeidx](https://togithub.com/almeidx), [@victorgdb](https://togithub.com/victorgdb), [@tinola](https://togithub.com/tinola), [@sampolahtinen](https://togithub.com/sampolahtinen), [@AikoRamalho](https://togithub.com/AikoRamalho), [@petradonka](https://togithub.com/petradonka) for helping!Automattic/mongoose (mongoose)
### [`v8.1.2`](https://togithub.com/Automattic/mongoose/blob/HEAD/CHANGELOG.md#812--2024-02-08) [Compare Source](https://togithub.com/Automattic/mongoose/compare/8.1.1...8.1.2) \================== - fix: include virtuals in document array toString() output if toObject.virtuals set [#14335](https://togithub.com/Automattic/mongoose/issues/14335) [#14315](https://togithub.com/Automattic/mongoose/issues/14315) - fix(document): handle setting nested path to spread doc with extra properties [#14287](https://togithub.com/Automattic/mongoose/issues/14287) [#14269](https://togithub.com/Automattic/mongoose/issues/14269) - fix(populate): call setter on virtual populated path with populated doc instead of undefined [#14314](https://togithub.com/Automattic/mongoose/issues/14314) - fix(QueryCursor): remove callback parameter of AggregationCursor and QueryCursor [#14299](https://togithub.com/Automattic/mongoose/issues/14299) [DevooKim](https://togithub.com/DevooKim) - types: add typescript support for arbitrary fields for the options parameter of Model functions which are of type MongooseQueryOptions [#14342](https://togithub.com/Automattic/mongoose/issues/14342) [#14341](https://togithub.com/Automattic/mongoose/issues/14341) [FaizBShah](https://togithub.com/FaizBShah) - types(model): correct return type for findOneAndUpdate with includeResultMetadata and lean set [#14336](https://togithub.com/Automattic/mongoose/issues/14336) [#14303](https://togithub.com/Automattic/mongoose/issues/14303) - types(connection): add type definition for `createCollections()` [#14295](https://togithub.com/Automattic/mongoose/issues/14295) [#14279](https://togithub.com/Automattic/mongoose/issues/14279) - docs(timestamps): clarify that replaceOne() and findOneAndReplace() overwrite timestamps [#14337](https://togithub.com/Automattic/mongoose/issues/14337) [#14309](https://togithub.com/Automattic/mongoose/issues/14309)Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - "after 9am and before 5pm Monday" (UTC).
🚦 Automerge: Enabled.
♻ 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.