Skip to content

[Snyk] Upgrade typeorm from 0.2.25 to 0.3.25#64

Open
csrausyan2 wants to merge 1 commit intomainfrom
snyk-upgrade-20edae0614bf63754a02eb6f0ce9d7e7
Open

[Snyk] Upgrade typeorm from 0.2.25 to 0.3.25#64
csrausyan2 wants to merge 1 commit intomainfrom
snyk-upgrade-20edae0614bf63754a02eb6f0ce9d7e7

Conversation

@csrausyan2
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade typeorm from 0.2.25 to 0.3.25.

ℹ️ 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 666 versions ahead of your current version.

  • The recommended version was released 2 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Prototype Pollution
SNYK-JS-HIGHLIGHTJS-1045326
290 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-HIGHLIGHTJS-1048676
290 No Known Exploit
medium severity Prototype Pollution
SNYK-JS-XML2JS-5414874
290 Proof of Concept
Release notes
Package name: typeorm
  • 0.3.25 - 2025-06-19

    What's Changed

    New Contributors

    Full Changelog: 0.3.24...0.3.25

  • 0.3.25-dev.eb3093d - 2025-06-05
  • 0.3.25-dev.ead4f98 - 2025-06-18
  • 0.3.25-dev.ce23d46 - 2025-06-16
  • 0.3.25-dev.b1e93f7 - 2025-06-18
  • 0.3.25-dev.af9ecc0 - 2025-06-17
  • 0.3.25-dev.a9c16ee - 2025-06-05
  • 0.3.25-dev.930eefd - 2025-06-06
  • 0.3.25-dev.86f12c9 - 2025-06-10
  • 0.3.25-dev.65d5a00 - 2025-06-05
  • 0.3.25-dev.63a3b9a - 2025-06-17
  • 0.3.25-dev.61753b1 - 2025-06-05
  • 0.3.25-dev.5003aaa - 2025-05-21
  • 0.3.25-dev.4b0ffee - 2025-06-06
  • 0.3.25-dev.42e7cbe - 2025-06-17
  • 0.3.25-dev.42913b9 - 2025-06-11
  • 0.3.25-dev.413f0a6 - 2025-06-05
  • 0.3.25-dev.2bfa300 - 2025-06-04
  • 0.3.25-dev.24c3e38 - 2025-06-05
  • 0.3.25-dev.12a71e4 - 2025-05-14
  • 0.3.25-dev.07d7913 - 2025-06-04
  • 0.3.25-dev.03faa78 - 2025-06-14
  • 0.3.24 - 2025-05-14

    What's Changed

    New Contributors

    Full Changelog: 0.3.23...0.3.24

  • 0.3.24-dev.e9eaf79 - 2025-05-13
  • 0.3.24-dev.d325d9e - 2025-05-14
  • 0.3.24-dev.c464ff8 - 2025-05-09
  • 0.3.24-dev.b8dbca5 - 2025-05-14
  • 0.3.24-dev.a6b61f7 - 2025-05-13
  • 0.3.24-dev.a213bbd - 2025-05-09
  • 0.3.24-dev.9f889b3 - 2025-05-13
  • 0.3.24-dev.80e9b30 - 2025-05-07
  • 0.3.24-dev.6d1c4f0 - 2025-05-12
  • 0.3.24-dev.39a6562 - 2025-05-12
  • 0.3.24-dev.15de733 - 2025-05-11
  • 0.3.24-dev.144634d - 2025-05-13
  • 0.3.24-dev.1198dc2 - 2025-05-12
  • 0.3.24-dev.2168441 - 2025-05-11
  • 0.3.23 - 2025-05-07

    ⚠️ Note on a breaking change

    This release includes a technically breaking change (from this PR) in the behaviour of the delete and update methods of the EntityManager and Repository APIs, when an empty object is supplied as the criteria:

    await repository.delete({})
    await repository.update({}, { foo: 'bar' })
    • Old behaviour was to delete or update all rows in the table
    • New behaviour is to throw an error: 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:

    await repository.createQueryBuilder().delete().execute()
    // executes: DELETE FROM table_name
    await repository.createQueryBuilder().update().set({ foo: 'bar' }).execute()
    // executes: UPDATE table_name SET foo = 'bar'

    An alternative method for deleting all rows is to use:

    await repository.clear()
    // executes: TRUNCATE TABLE table_name

    What's Changed

    New Contributors

    Full Changelog: 0.3.22...0.3.23

  • 0.3.23-dev.fe71a0c - 2025-04-15
  • 0.3.23-dev.fadad1a - 2025-05-01
  • 0.3.23-dev.cebd63b - 2025-04-03
  • 0.3.23-dev.c15cb07 - 2025-04-05
  • 0.3.23-dev.b9ddd14 - 2025-04-25
  • 0.3.23-dev.b9842e3 - 2025-04-30
  • 0.3.23-dev.b94dfb3 - 2025-05-06
  • 0.3.23-dev.a61654e - 2025-04-29
  • 0.3.23-dev.9464e65 - 2025-04-30
  • 0.3.23-dev.7c5ea99 - 2025-04-04
  • 0.3.23-dev.6ebae3b - 2025-04-03
  • 0.3.23-dev.6c5668b - 2025-04-03
  • 0.3.23-dev.673f065 - 2025-04-15
  • 0.3.23-dev.61a6f97 - 2025-04-25
  • 0.3.23-dev.56f1898 - 2025-04-15
  • 0.3.23-dev.4c8fc3a - 2025-04-16
  • 0.3.23-dev.45577df - 2025-04-14
  • 0.3.23-dev.3ffeea5 - 2025-05-05
  • 0.3.23-dev.274bdf2 - 2025-05-02
  • 0.3.23-dev.24a0369 - 2025-04-17
  • 0.3.23-dev.184f463 - 2025-04-15
  • 0.3.23-dev.055eafd - 2025-04-03
  • 0.3.23-dev.04f3d3f - 2025-04-04
  • 0.3.22 - 2025-04-03

    What's Changed

    • fix: transaction not ending correctly by @ alumni in #11264
    • docs: add "How to use Vite for the backend" entry to faq by @ robkorv in #11306
    • chore: don't use version in docker-compose files by @ assapir in #11320
    • fix(sap): pass the configured schema to the db client by

Snyk has created this PR to upgrade typeorm from 0.2.25 to 0.3.25.

See this package in npm:
typeorm

See this project in Snyk:
https://app.snyk.io/org/noieda/project/b71e5bd9-6444-4cef-aa06-577057a47ed0?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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants