27.0.0

@metamask/connect-evm 0.10.0

Changed

• Bump @metamask/connect-multichain to ^0.12.0 (#261)

@metamask/connect-multichain 0.12.0

Added

• Include analytics.remote_session_id in V2 connection metadata so the wallet can correlate dapp-side and wallet-side analytics events (#256)

@metamask/connect-solana 0.8.0

Added

• Add optional analytics.integrationType param to createSolanaClient() (#260)

@metamask/browser-playground 0.6.3

Changed

• Bump workspace dependencies:
  • @metamask/connect-evm@0.10.0
  • @metamask/connect-multichain@0.12.0

Fixed

• Fix @metamask/connect/evm import path to use @metamask/connect-evm directly (#263)

26.0.0

@metamask/browser-playground 0.6.2

Fixed

• Fix potential stale closure in handleCheckboxChange and unconditional useEffect on session change (#257)

25.0.0

@metamask/connect-evm 0.9.1

Changed

• chore: align sub-package licenses with root ConsenSys 2022 license (#241)
• chore: turborepo (#239)

Fixed

• wallet_requestPermissions now correctly re-prompts account selection on MWP (mobile) without requiring a full disconnect/reconnect cycle. The request forwards forceRequest: true through to MWPTransport, which previously ignored it and silently returned the existing session. (#243)

@metamask/connect-multichain 0.11.1

Changed

• chore: align sub-package licenses with root ConsenSys 2022 license (#241)
• chore: turborepo (#239)

Fixed

• MWPTransport.connect() now accepts and forwards a forceRequest option. When true, onResumeSuccess skips the isSameScopesAndAccounts check and unconditionally sends wallet_createSession, allowing consumers to re-prompt account selection on an existing MWP session. Previously forceRequest was silently ignored, causing wallet_requestPermissions to no-op on mobile. (#243)
• Fix platform detection for Hermes-based React Native apps: isReactNative() now checks global.navigator.product before window.navigator.product, so modern RN environments where window is undefined correctly resolve to PlatformType.ReactNative instead of PlatformType.NonBrowser. This restores analytics for all React Native consumers — analytics were silently disabled because #setupAnalytics() only calls analytics.enable() for browser and ReactNative platforms (#238)

@metamask/connect-solana 0.7.1

Changed

• chore: align sub-package licenses with root ConsenSys 2022 license (#241)

@metamask/browser-playground 0.6.1

Added

• Add global localhost scopes (#250)

Changed

• Bump workspace dependencies: @metamask/connect-evm@0.9.1, @metamask/connect-multichain@0.11.1

24.0.0

@metamask/browser-playground 0.6.0

Changed

• Change LegacyEVM card's sendTransaction to have an address field and default it to the connected address (#247)
• Add localhost to wagmi's configured chains (#246)
• Bump wagmi from ^2.19.2 to ^3.5.0 and apply v3 migration changes: use useConnectors() instead of useConnect().connectors, useChains() instead of useSwitchChain().chains, and rename useAccount to useConnection (#233)
• Bump @wagmi/core from ^2.22.1 to ^3.4.0 (#233)
• Bump @tanstack/react-query from >=5.45.1 to ^5.90.21 (#233)
• Bump @tanstack/react-query-persist-client, @tanstack/query-sync-storage-persister, and @tanstack/react-query-devtools from 5.0.5 to latest (^5.90.24 / ^5.91.3) (#233)

23.0.0

@metamask/connect-evm 0.9.0

Changed

• Migrate metamask_accountsChanged and metamask_chainChanged subscriptions from transport.onNotification() to typed core.on()/core.off(), removing @ts-expect-error suppressions (#230)

Fixed

• EIP1193Provider.request() now re-surfaces the original numeric RPC error code as error.code on the thrown error, matching the EIP-1193 error shape expected by dApps, wagmi, and ethers.js. Previously error.code was always undefined. (#232)

@metamask/connect-multichain 0.11.0

Changed

• DefaultTransport now forwards all wallet notifications instead of filtering to only metamask_chainChanged and metamask_accountsChanged, matching MWPTransport behavior (#230)
• stateChanged is now emitted via the EventEmitter so client.on('stateChanged', cb) fires correctly (#230)
• SDKEvents type now includes explicit entries for metamask_accountsChanged, metamask_chainChanged, and stateChanged (#230)
• Mark @react-native-async-storage/async-storage peer dependency as optional — web/Node consumers no longer pull in the React Native toolchain (#234)
• getInfuraRpcUrls now includes Solana mainnet and devnet CAIP chain IDs in the generated RPC URL map (#235)
• Updated infuraRpcUrls to align with Infura's currently supported networks by removing deprecated testnets (Goerli variants, Mumbai, Palm testnet, Aurora) and adding new mainnet/testnet coverage across Base, Blast, zkSync, BSC/opBNB, Scroll, Mantle, Sei, Swellchain, Unichain, Hemi, MegaETH, Monad, and Celo Sepolia (#237)

Fixed

• RPCInvokeMethodErr now carries the original numeric RPC code from the wallet (rpcCode) and the original wallet-facing message (rpcMessage) as separate fields, so higher layers can re-surface them without losing them inside internal error formatting. (#232)
• RequestRouter now propagates the numeric RPC error code from wallet response errors and transport exceptions into RPCInvokeMethodErr, ensuring the code is not dropped during error wrapping. (#232)
• DefaultTransport now attaches the numeric RPC code to errors produced from window.postMessage responses, so it survives the transport boundary. (#232)

@metamask/connect-solana 0.7.0

Added

• Add getInfuraRpcUrls({ infuraApiKey, networks }) helper to generate Solana supportedNetworks entries (mainnet/devnet) for createSolanaClient (#235)

@metamask/browser-playground 0.5.1

Changed

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

22.0.0

@metamask/analytics 0.4.0

Changed

• use merged integration types in analytics (#223)

@metamask/connect-evm 0.8.0

Changed

• BREAKING getInfuraRpcUrls now accepts a single options object { infuraApiKey, chainIds? } instead of a positional infuraApiKey string. The optional chainIds parameter accepts hex chain IDs to filter the output (#211)
• use merged integration types in analytics (#223)

Fixed

• fix: Fix react-native-playground consumption of PACKAGE_VERSION build-time constant in connect packages (#221)

@metamask/connect-multichain 0.10.0

Changed

• BREAKING getInfuraRpcUrls now accepts a single options object { infuraApiKey, caipChainIds? } instead of a positional infuraApiKey string. The optional caipChainIds parameter filters the output to only the specified CAIP-2 chain IDs (#211)
• use merged integration types in analytics (#223)

Fixed

• fix: Fix react-native-playground consumption of PACKAGE_VERSION build-time constant in connect packages (#221)

@metamask/connect-solana 0.6.0

Fixed

• fix: Fix react-native-playground consumption of PACKAGE_VERSION build-time constant in connect packages (#221)

@metamask/browser-playground 0.5.0

Changed

• Update getInfuraRpcUrls calls to use new options object parameter (#211)

21.0.0

@metamask/browser-playground 0.4.2

Added

• Add integrationType: wagmi to wagmi metamask connector(#215)

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

19.0.0

@metamask/connect-evm 0.6.0

Added

• Bump @metamask/connect-multichain to ^0.8.0 (#203)

@metamask/connect-multichain 0.8.0

Added

• Enable ConnectMultichain to automatically handle wallet_sessionChanged events when MetaMask extension is detected (Desktop Chrome/Firefox, or Mobile In-App Browser) and preferExtension: true without needing the user to explicitly connect via ConnectMultichain.connect() (#198)

Changed

• Bump @metamask/mobile-wallet-protocol-core to ^0.4.0 (#201)
• Bump @metamask/mobile-wallet-protocol-dapp-client to ^0.3.0 (#201)

@metamask/connect-solana 0.4.0

Changed

• Bump @metamask/connect-multichain to ^0.8.0 (#203)

@metamask/browser-playground 0.4.0

Added

• Add Connect (window.ethereum) button (#198)

Changed

• Update wagmi MetaMask connector (#202)

18.0.0

@metamask/connect-multichain 0.7.0

Changed

• Correct README documentation across connect-solana, connect-evm, and connect-multichain to match actual API behaviour. (#194)
• Redact logs (#191)
• Pin eciesjs to exact version 0.4.17 (#188)

Fixed

• Fix uncaught exception in parseWalletError when the wallet returns error codes outside the EIP-1193 provider range (1000–4999), such as standard JSON-RPC codes like -32603 (Internal error). This prevented Solana request rejections from being handled gracefully. (#189)

@metamask/connect-solana 0.3.0

Changed

• Correct README documentation across connect-solana, connect-evm, and connect-multichain to match actual API behaviour. (#194)
• Add missing changelogs from Release/17.0.0 (#186)

Fixed

• Explicitly disconnect only Solana scopes when calling SolanaClient.disconnect(). Previously calling this function would result in the wallet connection being terminated entirely even if other ecosystems (evm, bitcoin, etc) were still connected (#193)

@metamask/browser-playground 0.3.1

Changed

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

@metamask/react-native-playground 0.1.3

Changed

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

Fixed

• Fix malformed reported dapp URL causing issues in the wallet (#187)