All migrations run in a single transaction — migrations must not open their own connections

[RUKAYAT-CODER]

TypeORM's default migrationsTransactionMode is all: every migration runs in one shared transaction. A migration that calls queryRunner.connection.createQueryRunner() opens a separate pooled connection that cannot see uncommitted tables created earlier in the run (this is exactly the fix-invoice-number-sequence failure fixed in #1195).

This is a footgun for future migrations: any migration that uses connection.createQueryRunner() (or does SELECT on tables created by an earlier migration in the same run) will fail from scratch.

Fix: document the constraint in the migrations README (prefer the passed queryRunner), and/or audit existing migrations for createQueryRunner() usage.

[Meet-hybrid]

I would like to contribute to this issue. I have experience with JavaScript/TypeScript, React, backend APIs, testing, Git, and software architecture. I will follow the acceptance criteria, add tests, and provide a focused pull request.

[grantfox-oss]

🦊 GrantFox — @Meet-hybrid has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1211)
2. Your PR will be reviewed by the rinafcode maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@Meet-hybrid's PR #1215 was approved and merged by @RUKAYAT-CODER.

🏆 @Meet-hybrid: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,825 total points). Track your full progress on GrantFox.

👏 Great work, @Meet-hybrid! Keep contributing to rinafcode.