Skip to content

deps(deps): bump the wallet group with 4 updates - #485

Open
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/wallet-db3a360496
Open

deps(deps): bump the wallet group with 4 updates#485
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/wallet-db3a360496

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 24, 2026

Copy link
Copy Markdown
Contributor

Bumps the wallet group with 4 updates: @reown/appkit, @reown/appkit-adapter-wagmi, viem and wagmi.

Updates @reown/appkit from 1.8.19 to 1.8.23

Release notes

Sourced from @​reown/appkit's releases.

@​reown/appkit-siwe@​1.8.23

Patch Changes

  • #5712 f2d2539 Thanks @​enesozturk! - Recover Coinbase Wallet from the EIP-1193 4100 ("Must call 'eth_requestAccounts' before other methods") error that could dead-end signing after a session restore.

    On an AppKit auto-restore, the Coinbase Wallet SDK provider keeps its accounts but drops its internal authorization — unlike wagmi's own reconnect, AppKit's restore reads eth_accounts without re-issuing eth_requestAccounts. Consumers that call .request() directly on the provider (rather than through wagmi's hooks) then failed the first signing RPC with 4100.

    The provider registration seam (syncProvider) now wraps Coinbase eip155 providers — keyed on the connector id, which is stable across the wagmi, ethers, and ethers5 adapters (the provider "type" is remapped to 'EXTERNAL' on most paths, so it can't be used to detect Coinbase). A 4100 then triggers a one-shot recovery: a single eth_requestAccounts re-authorization, an active-chain re-assert before an eth_sendTransaction retry (so the transaction can't broadcast on the wrong network after the handshake resets the SDK's chain), then exactly one retry. Non-4100 errors, rejected re-auth prompts, and non-Coinbase providers are unaffected. The wrapper is cached per provider instance so consumers keep a stable reference.

  • #5665 e5ee43c Thanks @​Khizr97! - Fix coinbasePreference option being ignored — 'all' and 'eoaOnly' now correctly use the coinbaseWallet connector (with QR code support) instead of always using baseAccount. 'smartWalletOnly' uses baseAccount. Regression introduced in PR #5269.

  • #5663 da65c78 Thanks @​Khizr97! - fix(ethers,ethers5): resolve walletProvider after account switch in modal

    useAppKitProvider returned a stale provider when switching accounts inside the modal. In the early-return path of connect(), connector.provider was never initialised, causing the base-client's accountChanged handler to skip syncProvider(). The provider is now resolved from ethersProviders before the event is emitted.

  • #5706 ccf0dcb Thanks @​ignaciosantise! - fix: persist the universal-link base as the WalletConnect deeplink choice when experimental_preferUniversalLinks is enabled, so session-request re-opens (handled by universal-provider) use the wallet's universal link instead of falling back to its native custom scheme

  • Updated dependencies [f2d2539, e5ee43c, da65c78, ccf0dcb]:

    • @​reown/appkit-utils@​1.8.23
    • @​reown/appkit-common@​1.8.23
    • @​reown/appkit-ui@​1.8.23
    • @​reown/appkit-wallet@​1.8.23
    • @​reown/appkit-controllers@​1.8.23

@​reown/appkit-scaffold-ui@​1.8.23

Patch Changes

  • #5712 f2d2539 Thanks @​enesozturk! - Recover Coinbase Wallet from the EIP-1193 4100 ("Must call 'eth_requestAccounts' before other methods") error that could dead-end signing after a session restore.

    On an AppKit auto-restore, the Coinbase Wallet SDK provider keeps its accounts but drops its internal authorization — unlike wagmi's own reconnect, AppKit's restore reads eth_accounts without re-issuing eth_requestAccounts. Consumers that call .request() directly on the provider (rather than through wagmi's hooks) then failed the first signing RPC with 4100.

    The provider registration seam (syncProvider) now wraps Coinbase eip155 providers — keyed on the connector id, which is stable across the wagmi, ethers, and ethers5 adapters (the provider "type" is remapped to 'EXTERNAL' on most paths, so it can't be used to detect Coinbase). A 4100 then triggers a one-shot recovery: a single eth_requestAccounts re-authorization, an active-chain re-assert before an eth_sendTransaction retry (so the transaction can't broadcast on the wrong network after the handshake resets the SDK's chain), then exactly one retry. Non-4100 errors, rejected re-auth prompts, and non-Coinbase providers are unaffected. The wrapper is cached per provider instance so consumers keep a stable reference.

  • #5665 e5ee43c Thanks @​Khizr97! - Fix coinbasePreference option being ignored — 'all' and 'eoaOnly' now correctly use the coinbaseWallet connector (with QR code support) instead of always using baseAccount. 'smartWalletOnly' uses baseAccount. Regression introduced in PR #5269.

  • #5663 da65c78 Thanks @​Khizr97! - fix(ethers,ethers5): resolve walletProvider after account switch in modal

    useAppKitProvider returned a stale provider when switching accounts inside the modal. In the early-return path of connect(), connector.provider was never initialised, causing the base-client's accountChanged handler to skip syncProvider(). The provider is now resolved from ethersProviders before the event is emitted.

  • #5706 ccf0dcb Thanks @​ignaciosantise! - fix: persist the universal-link base as the WalletConnect deeplink choice when experimental_preferUniversalLinks is enabled, so session-request re-opens (handled by universal-provider) use the wallet's universal link instead of falling back to its native custom scheme

  • Updated dependencies [f2d2539, e5ee43c, da65c78, ccf0dcb]:

... (truncated)

Commits
  • a211396 chore: version packages (#5714)
  • f2d2539 fix(controllers): recover Coinbase 4100 unauthorized signing at the provider ...
  • da65c78 fix(ethers,ethers5): resolve walletProvider after account switch in modal (#5...
  • e5ee43c fix(wagmi): respect coinbasePreference when selecting Coinbase connector (#5665)
  • ccf0dcb fix: honor experimental_preferUniversalLinks on session-request re-opens (#5706)
  • a9d9c6c feat(siwx): tron verifier (#5688)
  • a409474 Release (#5705)
  • fb09a6d feat(appkit): expose headless resetWalletConnectUri + resetConnectingWallet (...
  • 6b9c313 feat(controllers): expose WalletConnect URI on public state for headless QR (...
  • a4b2d2f feat: expose headless wallet list imperatively on the AppKit client (#5695)
  • Additional commits viewable in compare view

Updates @reown/appkit-adapter-wagmi from 1.8.19 to 1.8.23

Release notes

Sourced from @​reown/appkit-adapter-wagmi's releases.

@​reown/appkit-adapter-wagmi@​1.8.23

Patch Changes

  • #5712 f2d2539 Thanks @​enesozturk! - Recover Coinbase Wallet from the EIP-1193 4100 ("Must call 'eth_requestAccounts' before other methods") error that could dead-end signing after a session restore.

    On an AppKit auto-restore, the Coinbase Wallet SDK provider keeps its accounts but drops its internal authorization — unlike wagmi's own reconnect, AppKit's restore reads eth_accounts without re-issuing eth_requestAccounts. Consumers that call .request() directly on the provider (rather than through wagmi's hooks) then failed the first signing RPC with 4100.

    The provider registration seam (syncProvider) now wraps Coinbase eip155 providers — keyed on the connector id, which is stable across the wagmi, ethers, and ethers5 adapters (the provider "type" is remapped to 'EXTERNAL' on most paths, so it can't be used to detect Coinbase). A 4100 then triggers a one-shot recovery: a single eth_requestAccounts re-authorization, an active-chain re-assert before an eth_sendTransaction retry (so the transaction can't broadcast on the wrong network after the handshake resets the SDK's chain), then exactly one retry. Non-4100 errors, rejected re-auth prompts, and non-Coinbase providers are unaffected. The wrapper is cached per provider instance so consumers keep a stable reference.

  • #5665 e5ee43c Thanks @​Khizr97! - Fix coinbasePreference option being ignored — 'all' and 'eoaOnly' now correctly use the coinbaseWallet connector (with QR code support) instead of always using baseAccount. 'smartWalletOnly' uses baseAccount. Regression introduced in PR #5269.

  • #5663 da65c78 Thanks @​Khizr97! - fix(ethers,ethers5): resolve walletProvider after account switch in modal

    useAppKitProvider returned a stale provider when switching accounts inside the modal. In the early-return path of connect(), connector.provider was never initialised, causing the base-client's accountChanged handler to skip syncProvider(). The provider is now resolved from ethersProviders before the event is emitted.

  • #5706 ccf0dcb Thanks @​ignaciosantise! - fix: persist the universal-link base as the WalletConnect deeplink choice when experimental_preferUniversalLinks is enabled, so session-request re-opens (handled by universal-provider) use the wallet's universal link instead of falling back to its native custom scheme

  • Updated dependencies [f2d2539, e5ee43c, da65c78, ccf0dcb]:

    • @​reown/appkit-utils@​1.8.23
    • @​reown/appkit@​1.8.23
    • @​reown/appkit-common@​1.8.23
    • @​reown/appkit-polyfills@​1.8.23
    • @​reown/appkit-scaffold-ui@​1.8.23
    • @​reown/appkit-wallet@​1.8.23
    • @​reown/appkit-controllers@​1.8.23

@​reown/appkit-adapter-wagmi@​1.8.22

Patch Changes

  • #5697 6b9c313 Thanks @​enesozturk! - Add a headless read for the WalletConnect URI, so a host can render a QR without the useAppKitWallets React hook.

    The AppKit instance now exposes getWalletConnectUri() — returning { wcUri, wcError, wcFetchingUri } — and subscribeWalletConnectUri(). Both read the connection layer directly (mirroring the existing getWalletList() / subscribeWalletList() pair), so a headless host gets the URI ungated through the instance without importing @reown/appkit-controllers (which can otherwise resolve to a different valtio singleton). This replaces the connection-level subscribeConnections, which is gated behind the multiWallet remote feature and so can't serve the URI for a single-wallet QR.

    Breaking: the imperative pre-fetch trigger previously named getWalletConnectUri() is renamed to prefetchWalletConnectUri(), freeing getWalletConnectUri() for the new read.

  • #5701 fb09a6d Thanks @​enesozturk! - Add headless reset methods for the WalletConnect URI + connecting-wallet state.

    The AppKit instance now exposes resetWalletConnectUri() and resetConnectingWallet() — thin passthroughs to HeadlessWalletUtil.resetWcUri() / resetConnectingWallet(). A headless host that reads the URI via getWalletConnectUri() can now clear it (e.g. when a QR is dismissed or a connection is cancelled) through the instance, without importing @reown/appkit-controllers. This completes the headless WalletConnect-URI surface alongside getWalletConnectUri / subscribeWalletConnectUri / prefetchWalletConnectUri.

  • #5695 a4b2d2f Thanks @​enesozturk! - Expose the headless wallet list imperatively on the AppKit client, so a non-React host can list / search / connect wallets without the useAppKitWallets React hook.

    New AppKit instance methods: fetchWallets(options?), getWalletList(), subscribeWalletList(cb), getWalletConnectUri(options?), and connectWallet(wallet, namespace?, options?). The shared imperative logic lives in a new HeadlessWalletUtil (@reown/appkit-controllers), which both the client methods and the React hook can use — one tested code path for headless wallet listing, search, pagination, the WalletConnect URI, and programmatic connect (injected / API / mobile-deeplink).

  • #5694 1c17897 Thanks @​enesozturk! - Fixed TRON tron_signTransaction payload shape to respect the wallet's tron_method_version session property. The connector now sends the spec-mandated legacy nested transaction.transaction shape by default, and the simplified flat shape only when the wallet advertises tron_method_version: "v1" in sessionProperties.

  • Updated dependencies [6b9c313, fb09a6d, a4b2d2f, 1c17897]:

... (truncated)

Commits
  • a211396 chore: version packages (#5714)
  • f2d2539 fix(controllers): recover Coinbase 4100 unauthorized signing at the provider ...
  • da65c78 fix(ethers,ethers5): resolve walletProvider after account switch in modal (#5...
  • e5ee43c fix(wagmi): respect coinbasePreference when selecting Coinbase connector (#5665)
  • ccf0dcb fix: honor experimental_preferUniversalLinks on session-request re-opens (#5706)
  • a9d9c6c feat(siwx): tron verifier (#5688)
  • a409474 Release (#5705)
  • fb09a6d feat(appkit): expose headless resetWalletConnectUri + resetConnectingWallet (...
  • 6b9c313 feat(controllers): expose WalletConnect URI on public state for headless QR (...
  • a4b2d2f feat: expose headless wallet list imperatively on the AppKit client (#5695)
  • Additional commits viewable in compare view

Updates viem from 2.47.6 to 2.55.19

Release notes

Sourced from viem's releases.

viem@2.55.19

Patch Changes

viem@2.55.18

Patch Changes

viem@2.55.17

Patch Changes

viem@2.55.16

Patch Changes

viem@2.55.15

Patch Changes

viem@2.55.13

Patch Changes

viem@2.55.11

Patch Changes

... (truncated)

Commits

Updates wagmi from 2.19.5 to 3.7.6

Release notes

Sourced from wagmi's releases.

wagmi@3.7.6

Patch Changes

  • Updated dependencies [77e4566]:
    • @​wagmi/connectors@​8.1.0

wagmi@3.7.5

Patch Changes

  • Updated dependencies [a3c5483]:
    • @​wagmi/connectors@​8.0.26

wagmi@3.7.4

Patch Changes

  • Breaking (wagmi/tempo): Removed Hooks.zone.useDepositStatus to align with the current Tempo Zone API. Use Hooks.zone.useWaitForTempoBlock to wait for a block import, or use Hooks.zone.useZoneInfo and inspect tempoBlockNumber for a one-shot read. (#5204)

  • Updated dependencies [0a8eb51, bfa70e3]:

    • @​wagmi/core@​3.6.4
    • @​wagmi/connectors@​8.0.25

wagmi@3.7.3

Patch Changes

  • Updated dependencies [57ac9b0]:
    • @​wagmi/core@​3.6.3
    • @​wagmi/connectors@​8.0.24

wagmi@3.7.2

Patch Changes

  • Fixed Tempo Zone hook compatibility with Viem 2.55.2. (#5198)

  • Updated dependencies [54497eb]:

    • @​wagmi/core@​3.6.2
    • @​wagmi/connectors@​8.0.23

wagmi@3.7.1

Patch Changes

  • Updated dependencies [18e9421]:
    • @​wagmi/core@​3.6.1
    • @​wagmi/connectors@​8.0.22

wagmi@3.7.0

Minor Changes

  • Breaking (wagmi/tempo): Updated Tempo APIs for viem 2.54.0: token balance and allowance reads now return Amount objects. (#5188)

Patch Changes

... (truncated)

Changelog

Sourced from wagmi's changelog.

3.7.6

Patch Changes

  • Updated dependencies [77e4566]:
    • @​wagmi/connectors@​8.1.0

3.7.5

Patch Changes

  • Updated dependencies [a3c5483]:
    • @​wagmi/connectors@​8.0.26

3.7.4

Patch Changes

  • Breaking (wagmi/tempo): Removed Hooks.zone.useDepositStatus to align with the current Tempo Zone API. Use Hooks.zone.useWaitForTempoBlock to wait for a block import, or use Hooks.zone.useZoneInfo and inspect tempoBlockNumber for a one-shot read. (#5204)

  • Updated dependencies [0a8eb51, bfa70e3]:

    • @​wagmi/core@​3.6.4
    • @​wagmi/connectors@​8.0.25

3.7.3

Patch Changes

  • Updated dependencies [57ac9b0]:
    • @​wagmi/core@​3.6.3
    • @​wagmi/connectors@​8.0.24

3.7.2

Patch Changes

  • Fixed Tempo Zone hook compatibility with Viem 2.55.2. (#5198)

  • Updated dependencies [54497eb]:

    • @​wagmi/core@​3.6.2
    • @​wagmi/connectors@​8.0.23

3.7.1

Patch Changes

  • Updated dependencies [18e9421]:
    • @​wagmi/core@​3.6.1
    • @​wagmi/connectors@​8.0.22

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the wallet group with 4 updates: [@reown/appkit](https://github.com/reown-com/appkit), [@reown/appkit-adapter-wagmi](https://github.com/reown-com/appkit), [viem](https://github.com/wevm/viem) and [wagmi](https://github.com/wevm/wagmi/tree/HEAD/packages/react).


Updates `@reown/appkit` from 1.8.19 to 1.8.23
- [Release notes](https://github.com/reown-com/appkit/releases)
- [Commits](https://github.com/reown-com/appkit/compare/@reown/appkit@1.8.19...@reown/appkit@1.8.23)

Updates `@reown/appkit-adapter-wagmi` from 1.8.19 to 1.8.23
- [Release notes](https://github.com/reown-com/appkit/releases)
- [Commits](https://github.com/reown-com/appkit/compare/@reown/appkit-adapter-wagmi@1.8.19...@reown/appkit-adapter-wagmi@1.8.23)

Updates `viem` from 2.47.6 to 2.55.19
- [Release notes](https://github.com/wevm/viem/releases)
- [Commits](https://github.com/wevm/viem/compare/viem@2.47.6...viem@2.55.19)

Updates `wagmi` from 2.19.5 to 3.7.6
- [Release notes](https://github.com/wevm/wagmi/releases)
- [Changelog](https://github.com/wevm/wagmi/blob/main/packages/react/CHANGELOG.md)
- [Commits](https://github.com/wevm/wagmi/commits/wagmi@3.7.6/packages/react)

---
updated-dependencies:
- dependency-name: "@reown/appkit"
  dependency-version: 1.8.23
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: wallet
- dependency-name: "@reown/appkit-adapter-wagmi"
  dependency-version: 1.8.23
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: wallet
- dependency-name: viem
  dependency-version: 2.55.19
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: wallet
- dependency-name: wagmi
  dependency-version: 3.7.6
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: wallet
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Aug 24, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: automated, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@sonarqubecloud

Copy link
Copy Markdown

@leocagli

Copy link
Copy Markdown
Collaborator

No mergeo este PR: rompe el build. Y vale la pena decir dónde, porque no es en el código sino antes, en la instalación.

npm ci falla con ERESOLVE y ni siquiera llega a compilar:

npm error code ERESOLVE
npm error While resolving: wagmi@3.7.6
npm error Found: typescript@5.7.3
npm error   dev typescript@"5.7.3" from the root project
npm error Conflicting peer dependency: typescript@7.0.2
npm error   peerOptional typescript@">=5.9.3" from wagmi@3.7.6
npm ci failed after 2 attempt(s); not retrying further.

El repo fija typescript@5.7.3 como dependencia exacta (sin ^), y wagmi@3.7.6 pide >=5.9.3. npm no tiene forma de satisfacer las dos, así que aborta.

Lo mismo le pasa al #486, que trae @typescript-eslint/eslint-plugin@8.67.0 y choca por la misma razón. O sea que no son dos problemas: es uno solo, el pin de TypeScript, bloqueando dos grupos de actualizaciones a la vez.

Lo que hay que resolver primero es ese pin, y es una decisión de mantenimiento, no algo que Dependabot pueda hacer por su cuenta desde este PR:

  • Subir TypeScript a >=5.9.3 en el package.json raíz, en su propio PR, y verificar que el typecheck siga limpio. Recién ahí este PR y el deps(deps-dev): bump the test-tooling group with 6 updates #486 pasan a ser mergeables.
  • O agregar un overrides para el peer, que hace que instale pero deja el conflicto real sin resolver. No lo recomiendo en un repo que ya tiene el typecheck como check requerido: esconde el problema hasta que aparezca como un error de tipos raro más adelante.

Sugiero lo primero, y en este orden: PR de TypeScript, después este, después el #486.

Un aviso aparte que no tiene que ver con este PR: el check SonarCloud Analysis está rojo en todos los PRs del repositorio desde el 17 de agosto, por una configuración de SonarCloud y no por el código. Está documentado en la #491.

Leo Cagliero, programa Starmaker, Cosmos LATAM y Open Stellar.

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