MetaMask / MetaMask/metamask-extension

AssetsController upgrade from v36 to v38

Open
#26,913 0 comments 0 reactions 0 assignees View on GitHub
blocked
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### What is this about?

The `AssetsController` is behind by two major versions and needs to be updated.
Upgrade from v36 to v38.

[Blocked by NetworkController upgrade](https://github.com/MetaMask/metamask-extension/issues/26911)

### Scenario

n/a

### Design

n/a

### Technical Details

See description

### Threat Modeling Framework

n/a

### Acceptance Criteria

- `AssetsController` is on v38

### Stakeholder review needed before the work gets merged

- [X] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the AssetsController upgrade path and the linked NetworkController upgrade issue, which blocks this work. Confirm the current controller version and identify the existing upgrade pattern before making changes. Done means AssetsController is on v38 and the relevant automation checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend-api-design
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.