Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: only create or update the email / phone identity after it's been verified #1403

Merged
merged 3 commits into from
Feb 8, 2024

Conversation

kangmingtay
Copy link
Member

What kind of change does this PR introduce?

  • We only want to create / update the email / phone identity after it's been verified during the email change / phone change flow
  • Previously, the email / phone identity was created / updated immediately after the user update endpoint is called. This results in the identity being created before it's been confirmed.

@kangmingtay kangmingtay requested a review from a team as a code owner February 7, 2024 10:49
internal/api/verify.go Show resolved Hide resolved
internal/api/verify.go Show resolved Hide resolved
@kangmingtay kangmingtay merged commit 2d20729 into master Feb 8, 2024
5 checks passed
@kangmingtay kangmingtay deleted the km/fix-email-chagne branch February 8, 2024 16:23
kangmingtay added a commit that referenced this pull request Feb 8, 2024
kangmingtay added a commit that referenced this pull request Feb 8, 2024
hf pushed a commit that referenced this pull request Feb 8, 2024
hf pushed a commit that referenced this pull request Feb 8, 2024
…i… (#1407)

…t's been verified (#1403)"

This reverts commit 2d20729.

Reverting so it can be re-added again.
hf pushed a commit that referenced this pull request Feb 8, 2024
… verified (again) (#1409)

## What kind of change does this PR introduce?
* We only want to create / update the email / phone identity after it's
been verified during the email change / phone change flow
* Previously, the email / phone identity was created / updated
immediately after the user update endpoint is called. This results in
the identity being created before it's been confirmed.

Like #1403, but adding again.
J0 pushed a commit that referenced this pull request Feb 12, 2024
🤖 I have created a release *beep* *boop*
---


##
[2.139.2](v2.139.1...v2.139.2)
(2024-02-08)


### Bug Fixes

* improve perf in account linking
([#1394](#1394))
([8eedb95](8eedb95))
* OIDC provider validation log message
([#1380](#1380))
([27e6b1f](27e6b1f))
* only create or update the email / phone identity after it's been
verified ([#1403](#1403))
([2d20729](2d20729))
* only create or update the email / phone identity after it's been
verified (again)
([#1409](#1409))
([bc6a5b8](bc6a5b8))
* unmarshal is_private_email correctly
([#1402](#1402))
([47df151](47df151))
* use `pattern` for semver docker image tags
([#1411](#1411))
([14a3aeb](14a3aeb))


### Reverts

* "fix: only create or update the email / phone identity after i…
([#1407](#1407))
([ff86849](ff86849))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants