-
Notifications
You must be signed in to change notification settings - Fork 5.2k
chore: bump @metamask/base-controller
to ^8.0.0
#30251
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
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. |
0f1ad33
to
bc03b12
Compare
@metamaskbot update-policies |
Policies updated. 🧠 Learn how: https://lavamoat.github.io/guides/policy-diff/#what-to-look-for-when-reviewing-a-policy-diff |
Builds ready [9a6f95b]
Page Load Metrics (1788 ± 62 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
@@ -19,6 +19,7 @@ export const CronjobControllerInit: ControllerInitFunction< | |||
// with the expected type. | |||
// TODO: Look into the type mismatch. | |||
state: persistedState.CronjobController, | |||
// @ts-expect-error TODO: Resolve mismatch between base-controller versions. |
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.
What is the error here?
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.
Property '#private' in type 'RestrictedMessenger' refers to a different member that cannot be accessed from within type 'RestrictedMessenger'.
This error often occurs when there’s a major version mismatch in base-controller. It will be resolved once we upgrade the controller. In the meantime, we’re using the @ts-ignore rule to accommodate the new base-controller version.
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 to me, assuming you will follow up with other controller bumps and remove the @ts-expect-error
comments.
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.
LGTM, also assuming there'll be a follow-up to re-align the base-controller
on every controllers 👍
Description
This PR bumps
@metamask/base-controller
from^7.0.0
to^8.0.0
.Major changes on version v8 is removal of
BaseControllerV1
and oldmessenger
aliases. CHANGELOGOther minor bumps to align with
@metamask/base-controller
version (mostly package version updates).@metamask/accounts-controller
from^23.0.0
to^23.0.1
CHANGELOG@metamask/address-book-controller
from^6.0.0
to^6.0.3
CHANGELOG@metamask/announcement-controller
from^7.0.0
to^7.0.3
CHANGELOG@metamask/ens-controller
from^15.0.0
to^15.0.2
CHANGELOG@metamask/gas-fee-controller
from^22.0.1
to^22.0.3
CHANGELOG@metamask/keyring-controller
from^19.0.6
to^19.0.7
CHANGELOG@metamask/logging-controller
from^6.0.0
to^6.0.4
CHANGELOG@metamask/message-manager
from^12.0.0
to^12.0.1
CHANGELOG@metamask/multichain-transactions-controller
from^0.2.0
to^0.3.0
CHANGELOG@metamask/name-controller
from^8.0.0
to^8.0.3
CHANGELOG@metamask/notification-services-controller
from^0.19.0
to^0.20.1
CHANGELOG@metamask/permission-controller
from^11.0.0
to^11.0.6
CHANGELOG@metamask/permission-log-controller
from^3.0.1
to^3.0.1
CHANGELOG@metamask/phishing-controller
from^12.3.0
to^12.3.2
CHANGELOG@metamask/polling-controller
from^12.0.1
to^12.0.3
CHANGELOG@metamask/profile-sync-controller
from^6.0.0
to^7.0.1
CHANGELOG@metamask/rate-limit-controller
from^6.0.2
to^6.0.3
CHANGELOG@metamask/user-operation-controller
from^24.0.0
to^24.0.1
CHANGELOG@metamask/preferences-controller
from^15.0.1
to^15.0.2
CHANGELOGRelated issues
Fixes: #30248, #30155
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist