Skip to content

fix: Polish Card toast for 8.6.0 release - #33766

Merged
amandaye0h merged 1 commit into
mainfrom
toast-8.6.0/polish-card
Jul 29, 2026
Merged

fix: Polish Card toast for 8.6.0 release#33766
amandaye0h merged 1 commit into
mainfrom
toast-8.6.0/polish-card

Conversation

@amandaye0h

@amandaye0h amandaye0h commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Description

Polishes Card toast call sites for the 8.6.0 release so they align with the shared toast pattern (Confirmation icon, success/error icon colors, and default toast chrome instead of custom background colors).

Updates Card toast call sites (copy success, provisioning errors, asset selection, spending limit, money-account linkage, waitlist success) and splits the waitlist success copy into title + description locale strings.

Changelog

CHANGELOG entry: Polished toast styling for consistency in the 8.6.0 release

Related issues

Fixes:

Related toast polish PRs for 8.6.0:

Manual testing steps

Feature: Card toasts
  Scenario: waitlist success toast
    Given the user submits the card waitlist form successfully
    When the success toast appears
    Then it shows the short title and description with a Confirmation icon

Screenshots/Recordings

Before

Screen.Recording.2026-07-28.at.3.27.35.PM.mov

After

card-after.mov

Pre-merge author checklist

Performance checks (if applicable)

  • I've tested on Android
    • Ideally on a mid-range device; emulator is acceptable
  • I've tested with a power user scenario
    • Use these power-user SRPs to import wallets with many accounts and tokens
  • I've instrumented key operations with Sentry traces for production performance metrics

For performance guidelines and tooling, see the Performance Guide.

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.

Made with Cursor

Align Card toast call sites with the shared 8.6.0 toast polish pattern.

Co-authored-by: Cursor <cursoragent@cursor.com>
@amandaye0h amandaye0h self-assigned this Jul 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@metamask-ci metamask-ci Bot added the team-design-system All issues relating to design system in Mobile label Jul 24, 2026
@metamask-ci

metamask-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

PR template — items to address before "Ready for review"

Warnings — informational, address before merging:

  • Related issues section is empty. Add Fixes: #123 / Closes: <URL> / Refs: <Jira key>, or write a short rationale after the colon.

See docs/readme/ready-for-review.md for the full Definition of Ready for Review.

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Smart E2E Test Selection

  • Selected E2E tags: SmokeMoney
  • Selected Performance tags: None (no tests recommended)
  • Risk Level: low
  • AI Confidence: 92%
click to see 🤖 AI reasoning details

E2E Test Selection:
All changes are confined to the MetaMask Card feature area (app/components/UI/Card/) with minor UI/styling adjustments:

  1. useCardHomeActions.ts: Changed icon color from success.default to icon.default - cosmetic color change in a toast notification.
  2. useCardProvisioning.ts: Removed backgroundColor property from a toast notification - minor UI styling change.
  3. AssetSelectionBottomSheet.tsx: Removed backgroundColor from two toast notifications - minor UI styling changes.
  4. WaitlistFormModal.tsx: Added descriptionOptions to split the waitlist success toast into title + description - small functional change to toast display.
  5. useMoneyAccountCardLinkage.tsx: Removed Box wrapper around Spinner and Icon components - minor layout refactor with no functional impact.
  6. useSpendingLimit.ts: Removed backgroundColor from two toast notifications - minor UI styling changes.
  7. Locale files (all languages): Split success_toast string into success_toast (title) and success_toast_description (description) to match the WaitlistFormModal change.

All changes are isolated to the Card/Money feature. No shared components (navigation, modals, confirmations, controllers) are affected. SmokeMoney covers Card home screen, card management, and related flows. No other tags are warranted since there are no changes to swap confirmations, network, accounts, or other feature areas.

Performance Test Selection:
All changes are minor UI/styling adjustments to toast notifications within the Card feature and locale string restructuring. No performance-sensitive code paths (rendering loops, data fetching, state management, navigation) are affected. No performance test files were changed. No performance tags are warranted.

View GitHub Actions results

@sonarqubecloud

Copy link
Copy Markdown

Comment thread locales/languages/de.json
pull Bot pushed a commit to Reality2byte/metamask-mobile that referenced this pull request Jul 28, 2026
## **Description**

Polishes Metamask Assets toast call sites for the 8.6.0 release so they
align with the shared toast pattern (Confirmation icon, success/error
icon colors, and default toast chrome instead of custom background
colors).

Updates token-details copy and NFT autodetection success toasts to use
the Confirmation icon with success coloring.

## **Changelog**

CHANGELOG entry: Polished toast styling for consistency in the 8.6.0
release

## **Related issues**

Fixes:

Related toast polish PRs for 8.6.0:
- MetaMask#33765 — Design System Engineers
- MetaMask#33766 — Card
- MetaMask#33767 — Predict
- MetaMask#33769 — Money Movement
- MetaMask#33771 — Mobile Core UX
- MetaMask#33772 — Engagement
- MetaMask#33773 — Social AI
- MetaMask#33774 — Web3Auth
- MetaMask#33775 — Earn
- MetaMask#33791 — Watchlist

## **Manual testing steps**

```gherkin
Feature: Assets toasts
  Scenario: token address copied
    Given the user copies a token address from token details
    When the toast appears
    Then it uses the Confirmation icon with the success color
```

## **Screenshots/Recordings**

### **Before**



https://github.com/user-attachments/assets/27ace1cd-6dc8-4feb-96ea-0ae5b5050b42



### **After**



https://github.com/user-attachments/assets/77363454-050d-460d-a4ac-3a9db699854c



## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **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.

Made with [Cursor](https://cursor.com)

Co-authored-by: Cursor <cursoragent@cursor.com>
pull Bot pushed a commit to Reality2byte/metamask-mobile that referenced this pull request Jul 28, 2026
## **Description**

Polishes Earn toast call sites for the 8.6.0 release so they align with
the shared toast pattern (Confirmation icon, success/error icon colors,
and default toast chrome instead of custom background colors).

Updates the Cash mUSD empty-state Merkl claim error toast label to bold
for consistency with other plain toasts.

## **Changelog**

CHANGELOG entry: Polished toast styling for consistency in the 8.6.0
release

## **Related issues**

Fixes:

Related toast polish PRs for 8.6.0:
- MetaMask#33765 — Design System Engineers
- MetaMask#33766 — Card
- MetaMask#33767 — Predict
- MetaMask#33769 — Money Movement
- MetaMask#33770 — Metamask Assets
- MetaMask#33771 — Mobile Core UX
- MetaMask#33772 — Engagement
- MetaMask#33773 — Social AI
- MetaMask#33774 — Web3Auth
- MetaMask#33791 — Watchlist

## **Manual testing steps**

```gherkin
Feature: Cash claim error toast
  Scenario: Merkl claim error
    Given a Merkl claim error occurs on the Cash empty state
    When the toast appears
    Then the error label is bold
```

## **Screenshots/Recordings**

### **Before**



https://github.com/user-attachments/assets/18dbc467-9ee9-418a-9b64-3e051a0d10ca



### **After**



https://github.com/user-attachments/assets/eb07041e-f01b-4822-817f-d1e6e3bbe58e



## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **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.

Made with [Cursor](https://cursor.com)

Co-authored-by: Cursor <cursoragent@cursor.com>
pull Bot pushed a commit to Reality2byte/metamask-mobile that referenced this pull request Jul 28, 2026
## **Description**

Polishes Web3Auth toast call sites for the 8.6.0 release so they align
with the shared toast pattern (Confirmation icon, success/error icon
colors, and default toast chrome instead of custom background colors).

Updates the import-SRP success toast to use the Confirmation icon with
the theme success color.

## **Changelog**

CHANGELOG entry: Polished toast styling for consistency in the 8.6.0
release

## **Related issues**

Fixes:

Related toast polish PRs for 8.6.0:
- MetaMask#33765 — Design System Engineers
- MetaMask#33766 — Card
- MetaMask#33767 — Predict
- MetaMask#33769 — Money Movement
- MetaMask#33770 — Metamask Assets
- MetaMask#33771 — Mobile Core UX
- MetaMask#33772 — Engagement
- MetaMask#33773 — Social AI
- MetaMask#33775 — Earn
- MetaMask#33791 — Watchlist

## **Manual testing steps**

```gherkin
Feature: Import SRP toast
  Scenario: SRP imported successfully
    Given the user successfully imports a secret recovery phrase
    When the success toast appears
    Then it uses the Confirmation icon with the success color
```

## **Screenshots/Recordings**

### **Before**



https://github.com/user-attachments/assets/3b4e9009-bf86-4df0-b012-faf210ebaa40



### **After**


https://github.com/user-attachments/assets/09487e6e-4e41-4d68-8f86-a155bf7a1c63




## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **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.

Made with [Cursor](https://cursor.com)

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
pull Bot pushed a commit to Reality2byte/metamask-mobile that referenced this pull request Jul 28, 2026
## **Description**

Polishes Engagement toast call sites for the 8.6.0 release so they align
with the shared toast pattern (Confirmation icon, success/error icon
colors, and default toast chrome instead of custom background colors).

Updates notification copy-clipboard and push-notification onboarding
toasts to use Confirmation + success/default icon colors and shared
accessory spacing.

## **Changelog**

CHANGELOG entry: Polished toast styling for consistency in the 8.6.0
release

## **Related issues**

Fixes:

Related toast polish PRs for 8.6.0:
- MetaMask#33765 — Design System Engineers
- MetaMask#33766 — Card
- MetaMask#33767 — Predict
- MetaMask#33769 — Money Movement
- MetaMask#33770 — Metamask Assets
- MetaMask#33771 — Mobile Core UX
- MetaMask#33773 — Social AI
- MetaMask#33774 — Web3Auth
- MetaMask#33775 — Earn
- MetaMask#33791 — Watchlist

## **Manual testing steps**

```gherkin
Feature: Notification toasts
  Scenario: copy from notification details
    Given the user copies a value from a notification detail
    When the toast appears
    Then it uses the Confirmation icon with the success color
```

## **Screenshots/Recordings**

### **Before**



https://github.com/user-attachments/assets/6bc662e1-e36e-48ec-b093-62924433af77



### **After**



https://github.com/user-attachments/assets/eb9f5c07-546c-4165-ab61-84955173e096



## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **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.

Made with [Cursor](https://cursor.com)

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
pull Bot pushed a commit to Reality2byte/metamask-mobile that referenced this pull request Jul 28, 2026
## **Description**

Polishes Predict toast call sites for the 8.6.0 release so they align
with the shared toast pattern (Confirmation icon, success/error icon
colors, and default toast chrome instead of custom background colors).

Updates Predict place-order and cash-out toasts to use
Confirmation/Danger icons with theme success/error colors, and adjusts
unit tests accordingly.

## **Changelog**

CHANGELOG entry: Polished toast styling for consistency in the 8.6.0
release

## **Related issues**

Fixes:

Related toast polish PRs for 8.6.0:
- MetaMask#33765 — Design System Engineers
- MetaMask#33766 — Card
- MetaMask#33769 — Money Movement
- MetaMask#33770 — Metamask Assets
- MetaMask#33771 — Mobile Core UX
- MetaMask#33772 — Engagement
- MetaMask#33773 — Social AI
- MetaMask#33774 — Web3Auth
- MetaMask#33775 — Earn
- MetaMask#33791 — Watchlist

## **Manual testing steps**

```gherkin
Feature: Predict order toasts
  Scenario: successful place order
    Given the user places a prediction order successfully
    When the success toast appears
    Then it uses the Confirmation icon with the success color
```

## **Screenshots/Recordings**

### **Before**



https://github.com/user-attachments/assets/2d43e493-d681-4af4-bca2-3d0329e953dd



### **After**



https://github.com/user-attachments/assets/10421f3c-656e-42f1-841b-e141e8b6c14c



## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **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.

Made with [Cursor](https://cursor.com)

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
pull Bot pushed a commit to Reality2byte/metamask-mobile that referenced this pull request Jul 28, 2026
## **Description**

Polishes Mobile Core UX toast call sites for the 8.6.0 release so they
align with the shared toast pattern (Confirmation icon, success/error
icon colors, and default toast chrome instead of custom background
colors).

Updates Address QR / QR account display copy toasts and the Wallet
privacy-policy toast close control to match the shared toast polish
pattern.

## **Changelog**

CHANGELOG entry: Polished toast styling for consistency in the 8.6.0
release

## **Related issues**

Fixes:

Related toast polish PRs for 8.6.0:
- MetaMask#33765 — Design System Engineers
- MetaMask#33766 — Card
- MetaMask#33767 — Predict
- MetaMask#33769 — Money Movement
- MetaMask#33770 — Metamask Assets
- MetaMask#33772 — Engagement
- MetaMask#33773 — Social AI
- MetaMask#33774 — Web3Auth
- MetaMask#33775 — Earn
- MetaMask#33791 — Watchlist

## **Manual testing steps**

```gherkin
Feature: Core UX toasts
  Scenario: address copied
    Given the user copies an account address from QR account display
    When the toast appears
    Then it is an Icon toast with Confirmation + success color
```

## **Screenshots/Recordings**

### **Before**



https://github.com/user-attachments/assets/7f48d3a7-3dfb-4eae-ac30-f6db8dbd0766



### **After**



https://github.com/user-attachments/assets/cd9a5000-80a1-4380-abf3-d39152f0e4e6



## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **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.

Made with [Cursor](https://cursor.com)

Co-authored-by: Cursor <cursoragent@cursor.com>
@amandaye0h
amandaye0h added this pull request to the merge queue Jul 29, 2026
Merged via the queue into main with commit 2e849ad Jul 29, 2026
265 of 267 checks passed
@amandaye0h
amandaye0h deleted the toast-8.6.0/polish-card branch July 29, 2026 01:46
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 29, 2026
@metamask-ci metamask-ci Bot added the release-8.6.0 Issue or pull request that will be included in release 8.6.0 label Jul 29, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release-8.6.0 Issue or pull request that will be included in release 8.6.0 risk:medium AI analysis: medium risk size-S team-design-system All issues relating to design system in Mobile

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants