[dev] [tofikwest] tofik/portal-sign-in-email-otp-error

[github-actions]

This is an automated pull request to merge tofik/portal-sign-in-email-otp-error into dev.
It was created by the [Auto Pull Request] action.

[cursor]

PR Summary

Pass request headers to email OTP sign-in, adapt Better Auth config, and upgrade better-auth to 1.4.5.

• Auth/Login:
  • Pass request headers and enable asResponse in login.ts when calling auth.api.signInEmailOTP.
  • Fix error message typo for rate limiting.
• Better Auth Config:
  • Update advanced config to use advanced.database.generateId: false in lib/auth.ts.
• Dependencies:
  • Upgrade better-auth to ^1.4.5 in apps/portal/package.json and to 1.4.5 in root package.json; update lockfile.

^{Written by Cursor Bugbot for commit 390989d. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
app	Building	Preview	Comment	Dec 5, 2025 11:22pm
portal	Building	Preview	Comment	Dec 5, 2025 11:22pm

[graphite-app]

Graphite Automations

"Auto-assign PRs to Author" took an action on this PR • (12/05/25)

1 reviewer was added to this PR based on Mariano Fuentes's automation.

[cursor]

Bug: Missing response status check causes false login success

When using asResponse: true with auth.api.signInEmailOTP, the API returns a Response object instead of throwing on errors. The code ignores this response and unconditionally returns { success: true }, meaning failed OTP authentication (invalid/expired codes) will incorrectly report success to the client. Other usages of asResponse: true in the codebase properly check response.ok before considering the operation successful.

 

[claudfuen]

🎉 This PR is included in version 1.68.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀