fix(deps): update dependency typeorm to v0.3.24#399
Merged
Conversation
f8e2d1c to
43d247e
Compare
43d247e to
8bae811
Compare
8bae811 to
ba49eb1
Compare
ba49eb1 to
095362f
Compare
095362f to
692beb6
Compare
692beb6 to
b2eed07
Compare
b2eed07 to
95ec52e
Compare
95ec52e to
67f6d26
Compare
67f6d26 to
58f35f0
Compare
58f35f0 to
4c136e5
Compare
Keith-CY
approved these changes
May 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
0.3.17->0.3.24Release Notes
typeorm/typeorm (typeorm)
v0.3.24Compare Source
Bug Fixes
Features
Performance Improvements
v0.3.23Compare Source
This release includes a technically breaking change (from this PR) in the behaviour of the
deleteandupdatemethods of the EntityManager and Repository APIs, when an empty object is supplied as the criteria:Empty criteria(s) are not allowed for the delete/update method.Why?
This behaviour was not documented and is considered dangerous as it can allow a badly-formed object (e.g. with an undefined id) to inadvertently delete or update the whole table.
When the intention actually was to delete or update all rows, such queries can be rewritten using the QueryBuilder API:
An alternative method for deleting all rows is to use:
Bug Fixes
aggregatemethod's generic type to its returned cursor (#10754) (56f1898)Features
Performance Improvements
v0.3.22Compare Source
Bug Fixes
Features
Reverts
v0.3.21Compare Source
Bug Fixes
reflect-metadatatopeerDependenciesand set version to"^0.1.14 || ^0.2.0"(#10779) (e7649d2)Performance Improvements
v0.3.20Compare Source
Bug Fixes
Features
Reverts
v0.3.19Compare Source
Bug Fixes
Cannot read properties of undefined (reading 'sync')caused after glob package upgradev0.3.18Compare Source
Bug Fixes
@VirtualColumn(#10432) (b53e410), closes #10431update: falsein persistence (#10250) (f8fa1fd), closes #10249date-fnsin favor ofDayJs(#10306) (cf7147f)Features
Performance Improvements
BREAKING CHANGES
See: https://github.com/mongodb/node-mongodb-native/blob/HEAD/etc/notes/CHANGES\_6.0.0.md
| null,if all columns in your embed entity are nullable. Since database queries now return embedded property as
nullif all its column values are null.Configuration
📅 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.