Skip to content

Conversation

@lionellbriones
Copy link

Description

  • Warn users that wallets will be locked on all devices on password change flow
  • Inform users that password is changed recently on home page and unlock page

Open in GitHub Codespaces

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@github-actions
Copy link

github-actions bot commented May 14, 2025

CLA Signature Action:

Thank you for your submission, we really appreciate it. We ask that you all read and sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just by adding a comment to this pull request with this exact sentence:

I have read the CLA Document and I hereby sign the CLA

By commenting with the above message you are agreeing to the terms of the CLA. Your account will be recorded as agreeing to our CLA so you don't need to sign it again for future contributions to this repository.

2 out of 3 committers have signed the CLA.
@lionellbriones
@lwin-kyaw
@Nguyen Anh Tu

GitHub can't find an account for Nguyen Anh Tu.
You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

@lwin-kyaw lwin-kyaw changed the base branch from feat/protect-wallet-page-improvement to feat/reset-password-modal May 20, 2025 10:37
@lionellbriones lionellbriones force-pushed the feat/password-change-sync branch from 81e39ad to 648bebe Compare May 27, 2025 08:00
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.

3 participants