Release 0.113.1

[tudddorrr]

No description provided.

[claude]

PR Review: Release 0.113.1

The transaction wrapping in register.ts is well-executed. The fix correctly prevents orphaned players on session creation failure, moves email validation before any DB work, and hashes the password outside the transaction (avoids holding a DB connection during CPU-bound work). The createPlayerAuthActivity receiving the trx EM is a subtle but important correctness fix that ensures the activity is rolled back on failure.

---

2. Potential Bugs

minor: down() migration may not fully revert user_recovery_code FK

In SchemaSnapshotChanges.down() the FK is restored as on update no action on delete cascade. The old entity was @ManyToOne(() => User) with no deleteRule, which MikroORM defaults to on delete no action. A rollback would leave cascade-delete behavior intact. The down() appears to have updateRule and deleteRule inverted relative to the original state.

---

5. Test Coverage

minor: no test verifying error propagation through the transaction callback

PlayerCreationError and PricingPlanLimitError are now thrown inside em.transactional() via ctx.throw(). There is no new test confirming the expected 4xx status is still returned (not a 500) when an error is thrown from inside the transaction callback. Given this is a structural change to how errors escape the handler, a test similar to the new orphaned-player test would add confidence.

---

1, 3, 4. Code Quality / Performance / Security

No issues found. The @Index() addition on failed_at, cascade-delete rule on UserRecoveryCode, and the timeout bumps to 2s are all clean improvements.