-
Notifications
You must be signed in to change notification settings - Fork 5k
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.
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
chore: Update @metamask/gas-fee-controller
and peer deps
#28745
Conversation
@@ -241,7 +241,6 @@ | |||
"@expo/config-plugins/glob": "^10.3.10", | |||
"@solana/web3.js/rpc-websockets": "^8.0.1", | |||
"@metamask/message-manager": "^10.1.0", | |||
"@metamask/gas-fee-controller@npm:^15.1.1": "patch:@metamask/gas-fee-controller@npm%3A15.1.2#~/.yarn/patches/@metamask-gas-fee-controller-npm-15.1.2-db4d2976aa.patch", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This resolution was already unused. Not directly related to the bump here, but couldn't hurt to remove it.
Update the `@metamask/gas-fee-controller` package to v21 to satisfy the peer dependency on `@metamask/network-controller@^21.0.0`, and update the `@metamask/user-operation-controller` to satisfy its peer dependency upon `@metamask/gas-fee-controller`. Note that an older version of `@metamask/gas-fee-controller` (v18) remains in the dependency tree, but only because it's imported by `@metamask/smart-transaction-controller` for type reasons. It has no runtime impact on the application, so the associated peer dependency warnings from this older release can be ignored. This will be eliminated soon, in an upcoming PR. The updated `@metamask/user-operation-controller` still does not have its peer dependencies satisfied, but the problems are pre-existing. The `@metamask/keyring-controller` and `@metamask/transaction-controller` packages are head of where this package expects them to be. This is not made worse by this PR though, and will be addressed in a future PR.
eeb0bf4
to
aa8e265
Compare
@metamaskbot update-policies |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@metamask/[email protected] |
Policies updated. 🧠 Learn how: https://lavamoat.github.io/guides/policy-diff/#what-to-look-for-when-reviewing-a-policy-diff |
Builds ready [243ee18]
Page Load Metrics (1696 ± 80 ms)
Bundle size diffs [🚀 Bundle size reduced!]
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 🚀
Description
Update the
@metamask/gas-fee-controller
package to v21 to satisfy the peer dependency on@metamask/network-controller@^21.0.0
, and update the@metamask/user-operation-controller
to satisfy its peer dependency upon@metamask/gas-fee-controller
.Note that an older version of
@metamask/gas-fee-controller
(v18) remains in the dependency tree, but only because it's imported by@metamask/smart-transaction-controller
for type reasons. It has no runtime impact on the application, so the associated peer dependency warnings from this older release can be ignored. This will be eliminated soon, in an upcoming PR.The updated
@metamask/user-operation-controller
still does not have its peer dependencies satisfied, but the problems are pre-existing. The@metamask/keyring-controller
and@metamask/transaction-controller
packages are head of where this package expects them to be. This is not made worse by this PR though, and will be addressed in a future PR.Changelogs:
@metamask/gas-fee-controller@21
: https://github.com/MetaMask/core/blob/main/packages/gas-fee-controller/CHANGELOG.md#2100@metamask/user-operation-controller@16
: https://github.com/MetaMask/core/blob/main/packages/user-operation-controller/CHANGELOG.md#1600startPollingByNetworkClientId
was breaking, but the user operation controller had an override for that method so it was preserved (see here)Related issues
Related to https://github.com/MetaMask/MetaMask-planning/issues/3568
Manual testing steps
N/A
Screenshots/Recordings
N/A
Pre-merge author checklist
Pre-merge reviewer checklist