fix(auth): clarify updateUserById applies changes directly#2031
Merged
Conversation
mandarini
approved these changes
Jan 20, 2026
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
3 participants
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
Users expected
updateUserById({ email, email_confirm: false })to require user confirmation before applying the email change. The admin API intentionally applies changes directly.Problem
The documentation for
updateUserByIdandemail_confirm/phone_confirmwas ambiguous, leading users to believe settingemail_confirm: falsewould prevent immediate email updates.Solution
Clarified documentation:
updateUserById: "Changes are applied directly without confirmation flows"email_confirm: "Sets the user's email as confirmed when true, or unconfirmed when false"phone_confirm: "Sets the user's phone as confirmed when true, or unconfirmed when false"Related