fix: clear restored walletconnect connections on disconnect

[o-mid]

Summary

• After WalletConnect connect + refresh, wagmi can keep multiple restored walletConnect connections.
• A single Disconnect only drops the current one, so the UI stays connected until the user clicks again.
• Disconnect now clears every active connection in one click (useDisconnectAll).

Fixes #2401

Problem

RainbowKit registers multiple WalletConnect connectors that share id: "walletConnect". After refresh, reconnect can restore more than one. Wagmi's default disconnect() only removes the current connection and switches to the next, so the account UI remains connected.

Reproduction

1. Connect with WalletConnect (QR / mobile wallet)
2. Refresh
3. Wait for restore
4. Click Disconnect once
5. UI stays connected until another click (or refresh)

Root cause

Multi-wrapper WalletConnect connectors + wagmi disconnect-current semantics after reconnect.

Fix

Add useDisconnectAll and use it from Account / Chain / Connect disconnect paths.

Tests

• Regression: bare disconnect() leaves restored WC connections connected
• Regression: useDisconnectAll() clears all in one click
• pnpm test:unit run packages/rainbowkit/src/hooks/useDisconnectAll.test.tsx
• pnpm --filter @rainbow-me/rainbowkit typecheck

Compatibility

• No public API changes
• Disconnect still means "log out" for RainbowKit's single-account UI
• Does not attempt to address issue 2232 (duplicate connector/provider sync) unless proven separately

Test plan

• Connect via WalletConnect, disconnect without refresh → disconnects once
• Connect via WalletConnect, refresh, disconnect once → UI + wagmi disconnected
• Refresh after disconnect → does not restore the removed session
• Injected wallet connect/disconnect still works
• Unit tests above pass in CI

[vercel]

@o-mid is attempting to deploy a commit to the rainbowdotme Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1236816

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 18 packages

Name	Type
@rainbow-me/rainbowkit	Patch
example	Patch
@rainbow-me/rainbow-button	Patch
rainbowkit-next-app	Patch
site	Patch
with-create-react-app	Patch
with-next-app-i18n	Patch
with-next-app	Patch
with-next-custom-button	Patch
with-next-mint-nft	Patch
with-next-siwe-iron-session	Patch
with-next-siwe-next-auth	Patch
with-next-wallet-button	Patch
with-next	Patch
with-react-router	Patch
with-remix	Patch
with-vite	Patch
with-next-rainbow-button	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1236816c4e

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep cancelling pending wallet connections

When the WalletButton QR flow is still pending and the user closes the connect modal, wagmi has isConnecting set but has not added anything to config.state.connections yet; useDisconnectAll therefore snapshots an empty list and this call becomes a no-op. The previous no-argument disconnect() still forced wagmi's status back to disconnected, which is exactly what the comment above this line says the close handler needs, so this can leave the custom WalletButton stuck in its loading/disabled connecting state until the pending connect promise settles. Preserve the old no-connection fallback when cancelling an in-flight connect.

Useful? React with 👍 / 👎.