fix(email-otp): match upstream replacement ordering - #133
Draft
salasebas wants to merge 1 commit into
Draft
Conversation
Create replacement verifications before deleting existing values, and only delete then retry after a failed create. Cover database, secondary, and dual storage replacement behavior.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upstream parity
Pinned reference: Better Auth v1.6.23 at
9dfceee14021fc15a2fb93023f39635f25b0b5ba,packages/better-auth/src/plugins/email-otp/routes.ts.Root cause: Ruby unconditionally deleted the existing verification before creating its replacement. Upstream creates first and enters delete-plus-retry only when that create rejects.
Checks