Skip to content

Release/752.0.0 #7642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
cryptodev-2s merged 9 commits into from
Jan 15, 2026
Merged

Release/752.0.0 #7642

cryptodev-2s merged 9 commits into from
Jan 15, 2026
+409 −244

Conversation

@cryptodev-2s
Copy link
Contributor

@cryptodev-2s cryptodev-2s commented Jan 15, 2026 •
edited by cursor bot
Loading

Explanation

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Release scope

  • Introduces @metamask/connectivity-controller (0.1.0) and upgrades @metamask/network-controller to 29.0.0 (now depends on ConnectivityController)
  • Monorepo-wide bumps to @metamask/json-rpc-engine 10.2.1 and @metamask/eth-block-tracker 15.0.1
  • Transaction and polling stack updates: transaction-controller 62.9.2, gas-fee-controller 26.0.2, polling-controller 16.0.2, signature-controller 39.0.1
  • Cascading dependency bumps across controllers (e.g., assets-controllers 95.3.0, bridge-controller 64.5.1, bridge-status-controller 64.4.3, transaction-pay-controller 11.0.2, user-operation-controller 41.0.2, multichain-network-controller 3.0.2, selected-network-controller 26.0.2)
  • Aligns to accounts-controller 35.0.2 and updates related packages/changelogs and yarn.lock

Written by Cursor Bugbot for commit 1014302. This will update automatically on new commits. Configure here.

@cryptodev-2s cryptodev-2s marked this pull request as ready for review January 15, 2026 18:04
@cryptodev-2s cryptodev-2s requested review from a team as code owners January 15, 2026 18:05
@cryptodev-2s cryptodev-2s force-pushed the release/752.0.0 branch 8 times, most recently from 5af991f to 79edaa6 Compare January 15, 2026 18:19
mcmire
mcmire reviewed Jan 15, 2026
View reviewed changes
packages/network-enablement-controller/CHANGELOG.md

### Added

- Add `nativeAssetIdentifiers` state property that maps CAIP-2 chain IDs to CAIP-19-like native asset identifiers (e.g., `eip155:1/slip44:60`) ([#7609](https://github.com/MetaMask/core/pull/7609))
Copy link
Contributor

@mcmire mcmire Jan 15, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like a change is missing from this changelog:

Suggested change
- Add `nativeAssetIdentifiers` state property that maps CAIP-2 chain IDs to CAIP-19-like native asset identifiers (e.g., `eip155:1/slip44:60`) ([#7609](https://github.com/MetaMask/core/pull/7609))
- Add `nativeAssetIdentifiers` state property that maps CAIP-2 chain IDs to CAIP-19-like native asset identifiers (e.g., `eip155:1/slip44:60`) ([#7609](https://github.com/MetaMask/core/pull/7609))
- Add `initNativeAssetIdentifiers` method to populate `nativeAssetIdentifiers` state property ([#7609](https://github.com/MetaMask/core/pull/7609))
- This is designed to be called during controller initialization.

Copy link
Contributor Author

@cryptodev-2s cryptodev-2s Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed here 623418c

Copy link
Contributor Author

@cryptodev-2s cryptodev-2s Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

However I don't see in the PR 7609

Copy link
Contributor Author

@cryptodev-2s cryptodev-2s Jan 15, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or, it must had been added there on that PR, I see

Copy link
Contributor

@mcmire mcmire Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yeah sorry, I meant that it wasn't present in the original PR.

@cryptodev-2s cryptodev-2s requested a review from mcmire January 15, 2026 19:03
mcmire
mcmire approved these changes Jan 15, 2026
View reviewed changes
Copy link
Contributor

@mcmire mcmire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@cryptodev-2s cryptodev-2s added this pull request to the merge queue Jan 15, 2026
Merged via the queue into main with commit 4a1b947 Jan 15, 2026
294 checks passed
@cryptodev-2s cryptodev-2s deleted the release/752.0.0 branch January 15, 2026 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mcmire mcmire mcmire approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@cryptodev-2s @mcmire