chore: update @metamask/transaction-pay-controller#29302
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. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on:
|
|
@SocketSecurity ignore npm/@metamask/assets-controllers@104.3.0 |
| // eslint-disable-next-line @typescript-eslint/no-explicit-any | ||
| }) as MultichainAccountWallet<any>; |
There was a problem hiding this comment.
I think we could use a resolution to align the keyring-api version for all controllers (until we update all other deps) so we avoid doing this kind of type-cast.
Let me try that locally
There was a problem hiding this comment.
Indeed, could you instead use resolution:
diff --git a/package.json b/package.json
index 180a943a47..a40b116569 100644
--- a/package.json
+++ b/package.json
@@ -204,7 +204,8 @@
"@metamask/messenger@^0.3.0": "^1.0.0",
"@metamask/accounts-controller": "^37.2.0",
"@metamask/profile-sync-controller": "^28.0.2",
- "@metamask/transaction-controller@^63.0.0": "^64.2.0"
+ "@metamask/transaction-controller@^63.0.0": "^64.2.0",
+ "@metamask/keyring-api": "^23.0.1"
},
"dependencies": {
"@braze/react-native-sdk": "patch:@braze/react-native-sdk@npm%3A19.1.0#~/.yarn/patches/@braze-react-native-sdk-npm-19.1.0-076-reactmoduleinfo.patch",We're currently working on updating all clients to update all accounts deps, so we'll remove the resolutions once everything has been updated.
There was a problem hiding this comment.
Good point, I updated the PR.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9704c3e. Configure here.
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection: Performance Test Selection: |
|
|
✅ E2E Fixture Validation — Schema is up to date |
ccharly
left a comment
There was a problem hiding this comment.
LGTM for accounts (not tested)
| "@metamask/keyring-api@npm:^21.3.0": "21.6.0", | ||
| "@metamask/keyring-api@npm:^21.4.0": "21.6.0", | ||
| "@metamask/keyring-api@npm:^21.5.0": "21.6.0", | ||
| "@metamask/keyring-api@npm:^21.6.0": "23.0.1", | ||
| "@metamask/keyring-api@npm:^22.0.0": "23.0.1", | ||
| "@metamask/keyring-api@npm:^23.0.1": "23.0.1" |
There was a problem hiding this comment.
For tracking purposes: This is expected and we're going to re-align all accounts deps very soon!




Description
Update @metamask/transaction-pay-controller, to add change to accountOverride property.
Changelog
CHANGELOG entry:
Related issues
Ref: https://consensyssoftware.atlassian.net/browse/CONF-1187
Manual testing steps
Screenshots/Recordings
NA
Pre-merge author checklist
Performance checks (if applicable)
trace()for usage andaddTokenfor an exampleFor performance guidelines and tooling, see the Performance Guide.
Pre-merge reviewer checklist
Note
Medium Risk
Dependency bumps pull in newer
@metamask/*controller and keyring packages, which can subtly change transaction/payment and bridge behavior at runtime. App code changes are minimal, but lockfile/resolution shifts increase integration/regression risk.Overview
Upgrades
@metamask/transaction-pay-controllerto^19.3.0and updates the lockfile/resolutions to align on newer@metamask/*packages (notably@metamask/keyring-api23.0.1, plus related bridge/assets/keyring client/internal deps).Updates
accountsControllerTestUtils.tsto recognize Stellar (XlmAccountType.Account->XlmScope.Pubnet) when generating mock account scopes.Reviewed by Cursor Bugbot for commit e677792. Bugbot is set up for automated code reviews on this repo. Configure here.