696.0.0

@metamask/shield-controller 3.1.0

Added

• Added AuthorizationList in transaction init and log requests for 7702 transactions. (#7246)

Changed

• Move peer dependencies for controller and service packages to direct dependencies (#7209, #7220, #7236)
  • The dependencies moved are:
    • @metamask/signature-controller (^37.0.0)
    • @metamask/transaction-controller (^62.3.0)
  • In clients, it is now possible for multiple versions of these packages to exist in the dependency tree.
    • For example, this scenario would be valid: a client relies on @metamask/controller-a 1.0.0 and @metamask/controller-b 1.0.0, and @metamask/controller-b depends on @metamask/controller-a 1.1.0.
  • Note, however, that the versions specified in the client's package.json always "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.

@metamask/subscription-controller 5.1.0

Changed

• Removed minBalanceUSD field from the SubscriptionEligibility type. (#7248)
• Updated submitShieldSubscriptionCryptoApproval to handle change payment method transaction if subscription already existed (#7231)
• Bump @metamask/transaction-controller from ^62.0.0 to ^62.3.0 (#7215, #7220, #7236)
• Move peer dependencies for controller and service packages to direct dependencies (#7209)
  • The dependencies moved are:
    • @metamask/profile-sync-controller (^27.0.0)
  • In clients, it is now possible for multiple versions of these packages to exist in the dependency tree.
    • For example, this scenario would be valid: a client relies on @metamask/controller-a 1.0.0 and @metamask/controller-b 1.0.0, and @metamask/controller-b depends on @metamask/controller-a 1.1.0.
  • Note, however, that the versions specified in the client's package.json always "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.