chore: bump assets-controllers and phishing controller#26340
Conversation
|
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. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection: Performance Test Selection: |
|



Description
Changelog
CHANGELOG entry: bump assets-controllers and phishing-controller versions
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Medium Risk
Primarily dependency upgrades plus a new phishing-scan action routed through the controller messenger; risk is moderate due to behavior changes coming from external controller version bumps and new security-alerts API traffic.
Overview
Bumps
@metamask/assets-controllersto^100.0.2and@metamask/phishing-controllerto^16.3.0(with correspondingyarn.lockupdates).Wires the new
PhishingController:bulkScanTokensaction intogetMultichainAssetsControllerMessenger, and updates API test mocks to handlePOST https://security-alerts.api.cx.metamask.io/token/scan-bulk.Written by Cursor Bugbot for commit 908ef8a. This will update automatically on new commits. Configure here.