brave-core#34774merged 2026-03-18 into master by Douglashdaniel [Wallet]: Add Unshield Funds Button to Asset Menu Linked by: GitHub closing reference, “Resolves/Fixes” line in the PR description
Desktop 1.89.132: “Added an "Unshield funds" button on the token menu. (#53718)” changelog line
Android 1.89.135: “Added "Unshield funds" button on the token menu. (#53718)” changelog line
iOS 1.89.144: “Added "Unshield funds" button on the token menu. (#53718)” changelog line
Release notes are per platform. Lines come from each platform’s Stable changelog. A platform without an entry is not covered by these lines.
Validation
QA required (QA/Yes).
QA Pass-Win64 (Desktop only)
QA Pass-Android ARM (Android only)
QA Pass-iPhone (iOS only)
QA labels are Brave’s own validation records per OS. They are not independent verification by this tracker.
Target
1.89.x - Release
For closed issues Brave sets the milestone to the earliest version line it believes the change landed in, and renames milestones as branches move from Nightly to Beta to Release. This tracker shows it but relies on build ancestry and release notes for availability.
Whether a merged pull request in this group is an ancestor of the brave-core tag of each platform’s current build (from versions.brave.com). Code presence is not the same as a feature being exposed on that platform.
Platform
Release
Beta
Nightly
Desktop
Included1.97.59in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
Included1.98.47in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
Included1.100.5in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
Android
Included1.97.57in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
Included1.98.52in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
Included1.100.5in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
iOS
Included1.96.62in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
Included1.99.44in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
Included1.100.7in v1.96.61 (GitHub compare v1.96.61...b6f067d9: behind); later builds of the same history include it (brave-core#34774)
Platforms all Description Now that we have the ability to Unshield ZEC, we should add a Unshield funds button the Asset Menu like our Shield funds button [image]
Description Adds a Unshield funds button to the Asset Menu for Shielded ZEC assets Resolves Test plan: 1. Make sure you have a shielded ZEC account and some ZEC shielded 2. Navigate to the Portfolio and open the Asset Menu for Shield ZEC token 3. Click Unshield funds, it should route you to the Send screen ready for Unshielding 4. Follow the same steps from the Account Details page. [GitHub link omitted]
Timeline (5 of 8 events)
2026-03-18 17:19 Merged masterby Douglashdaniel
2026-03-18 17:19 Closed by Douglashdaniel
2026-03-18 17:19 Milestone set 1.90.x - Nightlyby github-actions
2026-03-18 22:05 Referenced by brave-core#34821by Douglashdaniel
Uplift of #34774 Resolves https://github.com/brave/brave-browser/issues/53718 Pre-approval checklist: - [x] You have tested your change on Nightly. - [ ] This contains text which needs to be translated. - [ ] There are more than 7 days before the release. - [ ] I've notified folks in #l10n on Slack that translations are needed. - [x] The PR milestones match the branch they are landing to. Pre-merge checklist: - [x] You have checked CI and the builds, lint, and tests all…
Timeline (3 of 6 events)
2026-03-23 13:44 Milestone set 1.89.x - Betaby kjozwiak
Merged into brave-core master on 2026-03-18. Only builds cut from master after this merge (Nightly first) can contain it; whether a published build does is checked per build (see build presence on the item). Beta and Release get it only after a branch cut or an uplift.