Skip to content

chore: version packages - #68

Merged
chybisov merged 1 commit into
mainfrom
changeset-release/main
Jul 27, 2026
Merged

chore: version packages#68
chybisov merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@bigmi/client@0.10.1

Patch Changes

  • #67 3532b51 Thanks @arentant! - Prevent UniSat reconnect from opening the extension popup on page load.

  • #70 f427391 Thanks @chybisov! - Stop the Binance, Bitget, OKX and OneKey connectors from opening their wallet extension on page load. connect() now honours isReconnecting and verifies authorization through passive getAccounts() access, matching the UniSat, Xverse and Unhosted connectors. Bitget and OKX additionally confirm the extension still exposes an account instead of trusting the connected storage shim alone, and getAccounts() returns an empty list rather than throwing when no account is exposed. All five connectors now report an account-less extension as ConnectorNotConnectedError instead of mislabelling it a user rejection: the try wraps only requestAccounts(), the one step a user can actually reject. This also fixes OKX persisting a disconnected shim — and so silently disabling its own auto-reconnect for good — when a reconnect found no accounts.

  • #66 8da5d88 Thanks @yasha-meursault! - Fix reconnect leaving a stale connection stub after reload. On the first successful reconnection the connections map is now rebuilt from scratch instead of copying the map rehydrated from storage under the previous session's connector uid, and current points at the freshly reconnected connector. When no connector reconnects, connections and current are reset alongside status: 'disconnected'. Matches wagmi's behavior.

  • #69 7ff01b5 Thanks @chybisov! - Stop reconnect from clearing a connection established by a concurrent connect() call. Reconnect runs on mount and polls for a wallet provider for up to 5s, so a user can connect manually while it is still in flight; the no-connector-reconnected reset now only applies when the store is still in the reconnecting/connecting state reconnect put it in. Matches wagmi's behavior.

@bigmi/react@0.9.1

Patch Changes

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from b78522f to c83fda2 Compare July 27, 2026 12:13
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from c83fda2 to 5529d2a Compare July 27, 2026 12:25
@chybisov
chybisov merged commit 62c1e68 into main Jul 27, 2026
1 check passed
@chybisov
chybisov deleted the changeset-release/main branch July 27, 2026 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant