[Snyk] Upgrade typeorm from 0.2.30 to 0.3.23 #21563
Open
Conversation
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
Snyk has created this PR to upgrade typeorm from 0.2.30 to 0.3.23. See this package in npm: typeorm See this project in Snyk: https://app.snyk.io/org/snyk-platform/project/438ecf63-493d-4811-a229-8ce7f83afeed?utm_source=github&utm_medium=referral&page=upgrade-pr
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.
Snyk has created this PR to upgrade typeorm from 0.2.30 to 0.3.23.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 624 versions ahead of your current version.
The recommended version was released 22 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-XML2JS-5414874
Release notes
Package name: typeorm
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:
What's Changed
aggregatemethod's generic parameter to its returned cursor by @ pringon in #10754New Contributors
Full Changelog: 0.3.22...0.3.23
What's Changed
@ VirtualColumnby @ alumni in #10927New Contributors
Full Changelog: 0.3.21...0.3.22
What's Changed