Release/1171.0.0 - #9771
Closed
n3ps wants to merge 2 commits into
Closed
Conversation
|
✅ No changelog changes needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation
Release
@metamask/client-utils@1.5.1so extension can consume the subject-scoped keyring send mapping fix from #9749.Packages
@metamask/client-utils1.5.0→1.5.1Changelog highlights (
@metamask/client-utils)frommovement when mapping keyring send activity, so multi-party Solana txs (e.g. bridge source legs) no longer surface another address's token as the sent asset (fix: scope keyring mapping to subject address #9749)@metamask/core-backend/@metamask/transaction-controllerdependency ranges (Release/1163.0.0 #9735)Checklist
Made with Cursor