The bug fix in #20536 wasn't necessary to include because the bug it
fixes was never in production. it was introduced in this release as
part of #17945.
* [skip e2e] Update changelog for v10.31.0
Co-authored-by: Dan J Miller <danjm.com@gmail.com>
* Update CHANGELOG.md
Co-authored-by: Frederik Bolding <frederik.bolding@gmail.com>
* Update CHANGELOG.md
Co-authored-by: Frederik Bolding <frederik.bolding@gmail.com>
* Update CHANGELOG.md
Co-authored-by: Frederik Bolding <frederik.bolding@gmail.com>
---------
Co-authored-by: Dan J Miller <danjm.com@gmail.com>
Co-authored-by: Frederik Bolding <frederik.bolding@gmail.com>
* Version v10.30.2
* Ensure the GasDetailsItem component can handle a tx with a maxPriorityFee of 0 (#19102)
* Ensure the GasDetailsItem component can handle a tx with a maxPriorityFee of 0
* Clean up code
* Update ui/components/app/gas-details-item/gas-details-item.js
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
---------
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
* Backport the `@metamask/message-manager` update to v5 (#19110)
The `@metamask/message-manager` update to v5 has been backported to the
v10.30.x release branch. This update includes three breaking changes,
but two (bump in minimum supported Node.js version, and change in type
from `Map` to `Record`) don't affect this project. The only breaking
change requiring changes was the addition of the `getCurrentChainId`
constructor parameter for the TypedMessageManger.
* Update changelog
---------
Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
Co-authored-by: Dan J Miller <danjm.com@gmail.com>
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
* [skip e2e] Update changelog for v10.30.0
* Remove MMI change and move terms of use addition to the 'Added' section
---------
Co-authored-by: Dan J Miller <danjm.com@gmail.com>
