prisma/prisma (@prisma/client)
### [`v5.3.1`](https://togithub.com/prisma/prisma/releases/tag/5.3.1)
[Compare Source](https://togithub.com/prisma/prisma/compare/5.3.0...5.3.1)
Today, we are issuing the `5.3.1` patch release.
##### Fix in Prisma Client
- [Duplicated keys in `metrics` properties](https://togithub.com/prisma/prisma/issues/21069)
### [`v5.3.0`](https://togithub.com/prisma/prisma/releases/tag/5.3.0)
[Compare Source](https://togithub.com/prisma/prisma/compare/5.2.0...5.3.0)
🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v5.3.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.3.0) about the release.** 🌟
##### Highlights
In this sprint, we’ve made bug fixes and overall improvements to Prisma Client. We’ve been working on a few projects that will be announced soon. Stay tuned for the upcoming releases for updates!
##### Improvements and bug fixes
We made the following changes:
##### Prisma Client improvements
- Validation for `undefined` values in arrays in `Json` fields
We added runtime validation for `undefined` values in arrays in `Json` fields. Prisma Client will now return an error when an array contains an `undefined` value. Therefore, we encourage you to add validation that either removes the value or transforms it to `null` if you stumble on the runtime validation:
```ts
// Query
await prisma.user.findMany({
where: {
// JSON field
preferences: [undefined, '"theme": "dark"', null, ]
}
})
// Example error message on running the query
Can not use `undefined` value within array. Use `null` or filter out `undefined` values
```
- Performance improvements for models with many unique fields
This release improves Prisma Client’s memory consumption for models with many `@unique` constraints. This was a regression from version 4.10.1, where in some cases, if a model had many unique constraints, Prisma Client would use up a lot of available memory.
- Fixed the segmentation fault error that used to occur on ARM64 Linux binary targets
- Metrics Preview feature improvements:
- We updated the counters and gauge properties
- We fixed the bug that caused the `prisma_pool_connections_open` metric to have a negative value in some cases.
##### Prisma Migrate improvements
- Fixed an introspection bug for MongoDB views. Previously, if a MongoDB database contained a view, `prisma db pull` would throw an error. We resolved this, and views are now ignored.
- Added the `PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK` environment variable that enables you to disable [advisory locking](https://www.prisma.io/docs/concepts/components/prisma-migrate/migrate-development-production#advisory-locking).
##### [VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) improvements
- Added support for rendering multi-line comments in tooltips when hovering on a block.
- Improved the auto-completion for composite types in other blocks.
- Added a Code Action that allows you to replace `SetDefault` with `NoAction` when using MySQL and the default/`foreignKeys` relation mode.
##### Fixes and improvements
##### Prisma Migrate
- [Percona-XtraDB-Cluster prohibits use of GET_LOCK with pxc_strict_mode = ENFORCING](https://togithub.com/prisma/prisma/issues/16020)
- [MongoDB views should be ignored introspecting the database](https://togithub.com/prisma/prisma/issues/16179)
- [Error in Connector on MongoDB executing listIndex: "system.views"](https://togithub.com/prisma/prisma/issues/17006)
- [`prisma migrate deploy`: `MariaDB doesn't yet support 'GET_LOCK in cluster (WSREP_ON=ON)'`](https://togithub.com/prisma/prisma/issues/19350)
##### Prisma Client
- [Remove all special cases for Data Proxy in our tests](https://togithub.com/prisma/prisma/issues/16101)
- [Segmentation fault on ARM64 Linux](https://togithub.com/prisma/prisma/issues/18510)
- [In the metrics feature a gauge & counter are swapped](https://togithub.com/prisma/prisma/issues/18760)
- [The prisma metrics `prisma_pool_connections_open` has a bug where it goes negative](https://togithub.com/prisma/prisma/issues/18761)
- [Prisma crashes with GraphQL queries of nested one-to-many relationship](https://togithub.com/prisma/prisma/issues/18787)
- [P1017 Server has closed the connection on linux_arm64](https://togithub.com/prisma/prisma/issues/19209)
- [`Error: socket hang up` on Linux/arm64](https://togithub.com/prisma/prisma/issues/19419)
- [Panic in Query Engine with SIGABRT signal (Debian Bookworm, engineType = binary)](https://togithub.com/prisma/prisma/issues/19743)
- [Prisma 5 drops `undefined` from Arrays when using Json fields with Postgres](https://togithub.com/prisma/prisma/issues/20325)
- [Suspected memory leak in Lambda function after upgrading from 4.10.1](https://togithub.com/prisma/prisma/issues/20799)
- [Error when generating - No unsupported field should reach that path](https://togithub.com/prisma/prisma/issues/20986)
##### Language tools (e.g. VS Code)
- [Models with multi line comments only show last line in tooltip](https://togithub.com/prisma/language-tools/issues/861)
- [Add VS Code quick fix / code action to replace `SetDefault` with `NoAction` when `provider = "mysql"` and `relationMode = "foreignKeys" | default`](https://togithub.com/prisma/language-tools/issues/1286)
- [Composite Types aren't offered as being auto-completable in other blocks](https://togithub.com/prisma/language-tools/issues/1495)
##### Credits
Huge thanks to [@alencardc](https://togithub.com/alencardc), [@Oreilles](https://togithub.com/Oreilles), [@christianledgard](https://togithub.com/christianledgard), [@skyzh](https://togithub.com/skyzh), [@alula](https://togithub.com/alula), [@michaelpoellath](https://togithub.com/michaelpoellath), [@RobertCraigie](https://togithub.com/RobertCraigie), [@stephenwade](https://togithub.com/stephenwade) for helping!
Automattic/mongoose (mongoose)
### [`v7.5.1`](https://togithub.com/Automattic/mongoose/blob/HEAD/CHANGELOG.md#751--2023-09-11)
[Compare Source](https://togithub.com/Automattic/mongoose/compare/7.5.0...7.5.1)
\==================
- fix: set default value for \_update when no update object is provided and versionKey is set to false [#13795](https://togithub.com/Automattic/mongoose/issues/13795) [#13783](https://togithub.com/Automattic/mongoose/issues/13783) [MohOraby](https://togithub.com/MohOraby)
- fix: avoid unexpected error when accessing null array element on discriminator array when populating [#13716](https://togithub.com/Automattic/mongoose/issues/13716) [ZSabakh](https://togithub.com/ZSabakh)
- types(schematypes): use DocType for instance method this [#13822](https://togithub.com/Automattic/mongoose/issues/13822) [#13800](https://togithub.com/Automattic/mongoose/issues/13800) [pshaddel](https://togithub.com/pshaddel)
- types: remove duplicated 'exists' method in Model interface in models.d.ts [#13818](https://togithub.com/Automattic/mongoose/issues/13818) [ohzeno](https://togithub.com/ohzeno)
- docs(model): replace outdated docs on deprecated findOneAndUpdate() overwrite option [#13821](https://togithub.com/Automattic/mongoose/issues/13821) [#13715](https://togithub.com/Automattic/mongoose/issues/13715)
- docs: add example of using `virtuals.pathsToSkip` option for `toObject()` and `toJSON()` [#13798](https://togithub.com/Automattic/mongoose/issues/13798) [RobertHunter-Pluto](https://togithub.com/RobertHunter-Pluto)
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.2.0
->5.3.1
18.17.12
->18.17.16
7.5.0
->7.5.1
5.2.0
->5.3.1
Release Notes
prisma/prisma (@prisma/client)
### [`v5.3.1`](https://togithub.com/prisma/prisma/releases/tag/5.3.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.3.0...5.3.1) Today, we are issuing the `5.3.1` patch release. ##### Fix in Prisma Client - [Duplicated keys in `metrics` properties](https://togithub.com/prisma/prisma/issues/21069) ### [`v5.3.0`](https://togithub.com/prisma/prisma/releases/tag/5.3.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.2.0...5.3.0) 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v5.3.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.3.0) about the release.** 🌟 ##### Highlights In this sprint, we’ve made bug fixes and overall improvements to Prisma Client. We’ve been working on a few projects that will be announced soon. Stay tuned for the upcoming releases for updates! ##### Improvements and bug fixes We made the following changes: ##### Prisma Client improvements - Validation for `undefined` values in arrays in `Json` fields We added runtime validation for `undefined` values in arrays in `Json` fields. Prisma Client will now return an error when an array contains an `undefined` value. Therefore, we encourage you to add validation that either removes the value or transforms it to `null` if you stumble on the runtime validation: ```ts // Query await prisma.user.findMany({ where: { // JSON field preferences: [undefined, '"theme": "dark"', null, ] } }) // Example error message on running the query Can not use `undefined` value within array. Use `null` or filter out `undefined` values ``` - Performance improvements for models with many unique fields This release improves Prisma Client’s memory consumption for models with many `@unique` constraints. This was a regression from version 4.10.1, where in some cases, if a model had many unique constraints, Prisma Client would use up a lot of available memory. - Fixed the segmentation fault error that used to occur on ARM64 Linux binary targets - Metrics Preview feature improvements: - We updated the counters and gauge properties - We fixed the bug that caused the `prisma_pool_connections_open` metric to have a negative value in some cases. ##### Prisma Migrate improvements - Fixed an introspection bug for MongoDB views. Previously, if a MongoDB database contained a view, `prisma db pull` would throw an error. We resolved this, and views are now ignored. - Added the `PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK` environment variable that enables you to disable [advisory locking](https://www.prisma.io/docs/concepts/components/prisma-migrate/migrate-development-production#advisory-locking). ##### [VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) improvements - Added support for rendering multi-line comments in tooltips when hovering on a block. - Improved the auto-completion for composite types in other blocks. - Added a Code Action that allows you to replace `SetDefault` with `NoAction` when using MySQL and the default/`foreignKeys` relation mode. ##### Fixes and improvements ##### Prisma Migrate - [Percona-XtraDB-Cluster prohibits use of GET_LOCK with pxc_strict_mode = ENFORCING](https://togithub.com/prisma/prisma/issues/16020) - [MongoDB views should be ignored introspecting the database](https://togithub.com/prisma/prisma/issues/16179) - [Error in Connector on MongoDB executing listIndex: "system.views"](https://togithub.com/prisma/prisma/issues/17006) - [`prisma migrate deploy`: `MariaDB doesn't yet support 'GET_LOCK in cluster (WSREP_ON=ON)'`](https://togithub.com/prisma/prisma/issues/19350) ##### Prisma Client - [Remove all special cases for Data Proxy in our tests](https://togithub.com/prisma/prisma/issues/16101) - [Segmentation fault on ARM64 Linux](https://togithub.com/prisma/prisma/issues/18510) - [In the metrics feature a gauge & counter are swapped](https://togithub.com/prisma/prisma/issues/18760) - [The prisma metrics `prisma_pool_connections_open` has a bug where it goes negative](https://togithub.com/prisma/prisma/issues/18761) - [Prisma crashes with GraphQL queries of nested one-to-many relationship](https://togithub.com/prisma/prisma/issues/18787) - [P1017 Server has closed the connection on linux_arm64](https://togithub.com/prisma/prisma/issues/19209) - [`Error: socket hang up` on Linux/arm64](https://togithub.com/prisma/prisma/issues/19419) - [Panic in Query Engine with SIGABRT signal (Debian Bookworm, engineType = binary)](https://togithub.com/prisma/prisma/issues/19743) - [Prisma 5 drops `undefined` from Arrays when using Json fields with Postgres](https://togithub.com/prisma/prisma/issues/20325) - [Suspected memory leak in Lambda function after upgrading from 4.10.1](https://togithub.com/prisma/prisma/issues/20799) - [Error when generating - No unsupported field should reach that path](https://togithub.com/prisma/prisma/issues/20986) ##### Language tools (e.g. VS Code) - [Models with multi line comments only show last line in tooltip](https://togithub.com/prisma/language-tools/issues/861) - [Add VS Code quick fix / code action to replace `SetDefault` with `NoAction` when `provider = "mysql"` and `relationMode = "foreignKeys" | default`](https://togithub.com/prisma/language-tools/issues/1286) - [Composite Types aren't offered as being auto-completable in other blocks](https://togithub.com/prisma/language-tools/issues/1495) ##### Credits Huge thanks to [@alencardc](https://togithub.com/alencardc), [@Oreilles](https://togithub.com/Oreilles), [@christianledgard](https://togithub.com/christianledgard), [@skyzh](https://togithub.com/skyzh), [@alula](https://togithub.com/alula), [@michaelpoellath](https://togithub.com/michaelpoellath), [@RobertCraigie](https://togithub.com/RobertCraigie), [@stephenwade](https://togithub.com/stephenwade) for helping!Automattic/mongoose (mongoose)
### [`v7.5.1`](https://togithub.com/Automattic/mongoose/blob/HEAD/CHANGELOG.md#751--2023-09-11) [Compare Source](https://togithub.com/Automattic/mongoose/compare/7.5.0...7.5.1) \================== - fix: set default value for \_update when no update object is provided and versionKey is set to false [#13795](https://togithub.com/Automattic/mongoose/issues/13795) [#13783](https://togithub.com/Automattic/mongoose/issues/13783) [MohOraby](https://togithub.com/MohOraby) - fix: avoid unexpected error when accessing null array element on discriminator array when populating [#13716](https://togithub.com/Automattic/mongoose/issues/13716) [ZSabakh](https://togithub.com/ZSabakh) - types(schematypes): use DocType for instance method this [#13822](https://togithub.com/Automattic/mongoose/issues/13822) [#13800](https://togithub.com/Automattic/mongoose/issues/13800) [pshaddel](https://togithub.com/pshaddel) - types: remove duplicated 'exists' method in Model interface in models.d.ts [#13818](https://togithub.com/Automattic/mongoose/issues/13818) [ohzeno](https://togithub.com/ohzeno) - docs(model): replace outdated docs on deprecated findOneAndUpdate() overwrite option [#13821](https://togithub.com/Automattic/mongoose/issues/13821) [#13715](https://togithub.com/Automattic/mongoose/issues/13715) - docs: add example of using `virtuals.pathsToSkip` option for `toObject()` and `toJSON()` [#13798](https://togithub.com/Automattic/mongoose/issues/13798) [RobertHunter-Pluto](https://togithub.com/RobertHunter-Pluto)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.