Release 1163.0.0 - #9734
Closed
OGPoyraz wants to merge 4 commits into
Closed
Conversation
|
✅ Changelogs updated and pushed. |
… transaction-pay-controller@26.1.0
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
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
1163.0.0with minor version bumps for:@metamask/transaction-controller69.3.0→69.4.0@metamask/transaction-pay-controller26.0.1→26.1.0@metamask/transaction-controller@69.4.0getEffectiveRecipientutility that returns the actual recipient of a transaction, decoding it from calldata for ERC-20/ERC-721/ERC-1155 token transfer methods wheretxParams.tois the token contract (#9699)strategyfield toMetamaskPayMetadatato persist the MetaMask Pay strategy used to fund the transaction (#9733)@metamask/transaction-pay-controller@26.1.0atomicfield onTransactionConfig/TransactionDatafor a generic non-atomic post-Relay flow (#9497)metamaskPay.strategymetadata (#9733)Dependency updates
16 packages had their
@metamask/transaction-controllerdependency range updated to^69.4.0with corresponding changelog entries under[Unreleased].References
getEffectiveRecipientutilitystrategyin TransactionController metamaskPay metadataChecklist
Note
Low Risk
Dependency and changelog-only release wiring; behavioral changes ship in the already-released minor versions, not in new code in this diff.
Overview
Release
1163.0.0cuts published versions and rolls dependency ranges across the monorepo; the diff is version/changelog/yarn.lockupdates, not new implementation in this PR.@metamask/transaction-controller@69.4.0documents additive API: exportedgetEffectiveRecipient(real transfer recipient from calldata for ERC-20/721/1155) and optionalstrategyonMetamaskPayMetadatafor MetaMask Pay funding strategy persistence.@metamask/transaction-pay-controller@26.1.0documentsatomiconTransactionConfig/TransactionDatafor a generic non-atomic post-Relay flow, and persisting quote strategy into transactionmetamaskPay.strategymetadata (aligned with transaction-controller).Sixteen workspace packages (assets, bridge, client-utils, earn, wallet, etc.) move
@metamask/transaction-controllerfrom^69.3.0(or lower in consolidated changelog lines) to^69.4.0, with matching[Unreleased]changelog entries referencing #9734.Reviewed by Cursor Bugbot for commit c9a7d05. Bugbot is set up for automated code reviews on this repo. Configure here.