fix(deps): upgrade typeorm to 0.3.29

[snyk-io]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	SQL Injection SNYK-JS-TYPEORM-17391479	726

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 SQL Injection

[snyk-io]

This major version upgrade from TypeORM 0.2.x to 0.3.x introduces significant and numerous breaking changes that require a considerable migration effort. Code modifications are mandatory.

Key Breaking Changes:

• DataSource Replaces Connection: The entire connection management API has been overhauled. createConnection, getConnection, and Connection are deprecated and replaced by a new DataSource object. All database connections must be reconfigured to use this new API.
• Find Method Signature Changes: The signatures for find methods like findOne and find have been changed for consistency and type safety. The findOne(id) shorthand has been removed. Queries must now use an options object, such as findOne({ where: { id } }). New, simpler methods like findBy and findOneBy have been introduced for basic queries.
• Repository and Manager Deprecations: getRepository() and getManager() are deprecated. You should now access repositories and the entity manager directly from your DataSource instance.
• CLI and Migration Changes: Due to the DataSource change, ormconfig.json is no longer supported. A data source file must be created to configure the CLI for tasks like migration generation and execution.
• Return Value Changes: findOne and QueryBuilder.getOne() now return null instead of undefined when no entity is found, which can impact existing conditional logic.

Recommendation:
This is a high-effort migration that cannot be completed with simple find-and-replace changes. Developers must carefully follow an official migration guide and refactor their data access layer. Allocate dedicated time for this upgrade, as it will involve significant code changes and thorough testing.

Source: GitHub Issue - Migration Guide, Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.