chore(deps): bump wagmi from 2.19.5 to 3.6.16

[dependabot]

Bumps wagmi from 2.19.5 to 3.6.16.

Release notes

Sourced from wagmi's releases.

wagmi@3.6.16

Patch Changes

• Updated dependencies [b029f1c, df7bd38, df7bd38]:
  • @​wagmi/connectors@​9.0.0
  • @​wagmi/core@​3.5.0

wagmi@3.6.15

Patch Changes

• Handled malformed cookie state in cookieToInitialState. (#5116)

• wagmi/tempo: Renamed Actions.wallet.send to Actions.wallet.transfer and Hooks.wallet.useSend to Hooks.wallet.useTransfer. (#5121)

  Also bumps the accounts peer dependency to ~0.12.

  - await Actions.wallet.send(config, {
  -   to: '0x...',
  -   token: '0x...',
  -   value: '1.5',
  - })
  + await Actions.wallet.transfer(config, {
  +   amount: '1.5',
  +   to: '0x...',
  +   token: '0x...',
  + })

  - const send = Hooks.wallet.useSend()
  + const transfer = Hooks.wallet.useTransfer()

• Updated dependencies [f1e6d70, 4c44cd0]:

  • @​wagmi/core@​3.4.12
  • @​wagmi/connectors@​8.0.14

wagmi@3.6.14

Patch Changes

• Updated dependencies [9e8418a]:
  • @​wagmi/core@​3.4.11
  • @​wagmi/connectors@​8.0.13

wagmi@3.6.13

Patch Changes

• Fixed useReadContracts to prefer an explicit chainId parameter over inferred or connected chain ids. (8c56235)

... (truncated)

Changelog

Sourced from wagmi's changelog.

3.6.16

Patch Changes

• Updated dependencies [b029f1c, df7bd38, df7bd38]:
  • @​wagmi/connectors@​9.0.0
  • @​wagmi/core@​3.5.0

3.6.15

Patch Changes

• Handled malformed cookie state in cookieToInitialState. (#5116)

• wagmi/tempo: Renamed Actions.wallet.send to Actions.wallet.transfer and Hooks.wallet.useSend to Hooks.wallet.useTransfer. (#5121)

  Also bumps the accounts peer dependency to ~0.12.

  - await Actions.wallet.send(config, {
  -   to: '0x...',
  -   token: '0x...',
  -   value: '1.5',
  - })
  + await Actions.wallet.transfer(config, {
  +   amount: '1.5',
  +   to: '0x...',
  +   token: '0x...',
  + })

  - const send = Hooks.wallet.useSend()
  + const transfer = Hooks.wallet.useTransfer()

• Updated dependencies [f1e6d70, 4c44cd0]:

  • @​wagmi/core@​3.4.12
  • @​wagmi/connectors@​8.0.14

3.6.14

Patch Changes

• Updated dependencies [9e8418a]:
  • @​wagmi/core@​3.4.11
  • @​wagmi/connectors@​8.0.13

3.6.13

... (truncated)

Commits

• 2f77dbc chore: version packages (#5140)
• c162248 chore: drop older TypeScript support (#5139)
• f44f781 dev: bump viem version
• 98f9a16 chore: version packages (#5122)
• 4c44cd0 refactor(tempo): rename wallet.send to wallet.transfer (#5121)
• dcd6f60 chore: version packages (#5118)
• 4351978 chore: version packages (#5114)
• 8c56235 close: #5106
• da855c6 chore: version packages (#5113)
• f5f498a test: remove blockTimestamp from snapshots
• Additional commits viewable in compare view

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
txkit-docs	Ready	Preview, Comment	Jun 8, 2026 6:28am
txkit-land	Ready	Preview, Comment	Jun 8, 2026 6:28am
txkit-story	Ready	Preview, Comment	Jun 8, 2026 6:28am

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm damerau-levenshtein is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/damerau-levenshtein@1.0.8 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/damerau-levenshtein@1.0.8. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm data-urls is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/data-urls@7.0.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/data-urls@7.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/entities@6.0.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@6.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm es-module-lexer is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@astrojs/mdx@5.0.4 → npm/es-module-lexer@2.0.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-module-lexer@2.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm es-module-lexer is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@astrojs/mdx@5.0.4 → npm/es-module-lexer@2.0.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-module-lexer@2.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report