20.0.0

@metamask/analytics 0.3.0

Changed

• BREAKING MMConnectProperties.mmconnect_versions type changed from string to Record<string, string> (#206)

@metamask/connect-evm 0.7.0

Added

• Enable specifying the integration type for analytics. Defaults to direct. (#213)
• Pass connect-evm package version to createMultichainClient via the versions option so it appears in analytics events (#206)

Fixed

• Fix an issue where connect would always return the default chain id regardless of other chains being specified. This also affected connectWith and connectAndSign (#205)

@metamask/connect-multichain 0.9.0

Added

• Add versions constructor option to createMultichainClient so chain-specific packages (connect-evm, connect-solana) can report their version in analytics events. Versions are merged into the singleton on each call, following the same pattern as api.supportedNetworks. (#206)

Changed

• BREAKING mmconnect_versions analytics property is now a Record<string, string> keyed by package name instead of a plain version string (#206)

Removed

• Stop passing sdkVersion to install and OTP modals (#212)

Fixed

• Fix a bug where wallet_sessionChanged events were failing to propagate to the ConnectMultichain instance when the DefaultTransport is using the WindowPostMessageTransport. This was affecting Firefox, both iOS and Android in-app browsers (#204)

@metamask/connect-solana 0.5.0

Added

• Pass connect-solana package version to createMultichainClient via the versions option so it appears in analytics events (#206)

@metamask/multichain-ui 0.4.0

Removed

• Remove SDK version label from install and OTP modals (#212)
• BREAKING Remove sdkVersion prop from mm-install-modal and mm-otp-modal components (#212)

@metamask/browser-playground 0.4.1

Added

• Add Connect button that calls legacy EVM connectAndSign method (#205)

Changed

• Bump workspace dependencies:
  • @metamask/connect-evm@0.7.0
  • @metamask/connect-multichain@0.9.0