Repository navigation
chore: Bump gas-fee-controller to 27.1.1 - #47821
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. |
6e283bd to
4e12042
Compare
|
@metamaskbot update-policies |
|
Policies updated. Tip Follow the policy review process outlined in the LavaMoat Policy Review Process doc before expecting an approval from Policy Reviewers. 👀 lavamoat/webpack/mv2/beta/policy.json changes differ from lavamoat/webpack/mv2/main/policy.json changes |
✨ Files requiring CODEOWNER review ✨📜 @MetaMask/policy-reviewers (8 files, +296 -312)
Tip Follow the policy review process outlined in the LavaMoat Policy Review Process doc before expecting an approval from Policy Reviewers. |
|
@metamaskbot update-policies |
|
Policies updated. Tip Follow the policy review process outlined in the LavaMoat Policy Review Process doc before expecting an approval from Policy Reviewers. 👀 lavamoat/webpack/mv2/beta/policy.json changes differ from lavamoat/webpack/mv2/main/policy.json changes |
Builds ready [6420530]
⚡ Performance Benchmarks (Total: 🟢 11 pass · 🟡 0 warn · 🔴 0 fail)
Bundle Size Diffs [🚀 Bundle size reduced!]
|
Builds ready [bb348ca]
⚡ Performance Benchmarks (Total: 🟢 7 pass · 🟡 2 warn · 🔴 4 fail)
Bundle Size Diffs [🚨 Warning! Bundle size has increased!]
|
|
|
No release label on PR. Adding release label release-13.58.0 on PR, as PR was added to branch 13.58.0 when release was cut. |



Description
Currently, we are using
@metamask/gas-fee-controller26.1.0, when the latest version is 27.1.1. This blocks an initiative by the Core Platform team to streamline the background<->UI connection API so that it goes through the root messenger instead of a bespoke object (as not all GasFeeController methods that should be registered through the messenger actually are). This PR bumpsgas-fee-controlleraccordingly.The good news is that GasFeeController is initialized through the
walletpackage, which is already using 27.1.1. We do import some types throughgas-fee-controllerdirectly, but none of the breaking changes between 26.x and 27.x affect how they're used, so there's nothing we need to adapt to.You can view the changelog for
gas-fee-controllerhere.Changelog
CHANGELOG entry: null
Related issues
https://consensyssoftware.atlassian.net/browse/WPC-1584
Manual testing steps
This PR should have no functional changes. All flows should work as-is.
Screenshots/Recordings
(N/A)
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Low Risk
Dependency version and LavaMoat policy updates only; no runtime code changes in the diff.
Overview
Bumps
@metamask/gas-fee-controllerfrom 26.1.0 to 27.1.1 inpackage.jsonand the lockfile, with no application source edits in this PR.LavaMoat webpack policies (mv2/mv3 variants) are regenerated to match the new dependency graph: gas-fee-controller now uses package-scoped entries for its nested deps (e.g.
@metamask/gas-fee-controller>@metamask/controller-utils, polling,uuid), duplicate nested policies for transaction-controller/wallet-specific gas-fee bundles are removed in favor of the shared@metamask/gas-fee-controllerentry, and@metamask/user-operation-controller>@metamask/gas-fee-controlleris added where that controller bundles its own copy.This aligns the extension with the version already used via
walletso messenger-based background↔UI wiring for gas fees can move forward without a functional behavior change expected from the bump alone.Reviewed by Cursor Bugbot for commit bb348ca. Bugbot is set up for automated code reviews on this repo. Configure here.