fix(deps): update dependency @wagmi/connectors to v5.11.2 #36

#4691 a03da817a388646c9b4885792101a67eef3616e7 Thanks @frolic! - Fixed walletConnect#connect by moving chain switch directly inside instead of relying on getProvider.

`v5.9.6`

Compare Source

Patch Changes

Updated dependencies [d4c367ca46c508598c997cf229a31593a1e2b8b8]:
- @wagmi/core@2.20.1

`v5.9.5`

Compare Source

Patch Changes

Updated dependencies [a13aa2b68890f180f6ac3f741cbb9817494cb66c]:
- @wagmi/core@2.20.0

`v5.9.4`

Compare Source

Patch Changes

#4764 f4039419b83b52b2984de149db85c11f503ffe39 Thanks @mikelxc! - Updated gemini connector

`v5.9.3`

Compare Source

Patch Changes

#4759 909324d28c81e15c9df312b277dcff1983fbae4d Thanks @mikelxc! - Added Gemini

`v5.9.2`

Compare Source

Patch Changes

Updated dependencies [b5f017dbc707729eb0b36d617352be224d1139d4]:
- @wagmi/core@2.19.0

`v5.9.1`

Compare Source

Patch Changes

6fbafd425e488dbeee8404162dbeb3c737eeb8cf Thanks @jxom! - Updated @base-org/account
Updated dependencies [6514ba29a5acb918773235fed0238d7d679d06d5]:
- @wagmi/core@2.18.1

`v5.9.0`

Compare Source

Minor Changes

#4734 eac550ae5b49f96a7e3404a6d88adc62d3889013 Thanks @jxom! - Added baseAccount connector.

Patch Changes

Updated dependencies [eac550ae5b49f96a7e3404a6d88adc62d3889013]:
- @wagmi/core@2.18.0

`v5.8.6`

Compare Source

Patch Changes

#4731 e75bd89406e9b6ff5b7d3a7148ab34140fe6352a Thanks @tomiir! - Updated @coinbase/wallet-sdk to version 4.3.6

`v5.8.5`

Compare Source

Patch Changes

Updated dependencies [7ce242b549d8cc78e6c319d9ee419693da36704c]:
- @wagmi/core@2.17.3

`v5.8.4`

Compare Source

Patch Changes

#4696 3a90f358820444a85bb727742b0a16eb943fc361 Thanks @tomiir! - Updated @walletconnect/etereum-provider to version 2.21.1

`v5.8.3`

Compare Source

Patch Changes

#4660 42b1fed58e9ac09da0f8ebf3e9271f98a707aaac Thanks @ganchoradkov! - Updated @walletconnect/ethereum-provider version to 2.20.2

`v5.8.2`

Compare Source

Patch Changes

Updated dependencies [29297a48af72b537173d948ccd2fe37d39914c66, 07370106d5fb6b8fe300992d93abf25b3d0eaf57]:
- @wagmi/core@2.17.2

`v5.8.1`

Compare Source

Patch Changes

Updated dependencies [01f64e64fa4f85cdd30023903f972f4f9023681f]:
- @wagmi/core@2.17.1

`v5.8.0`

Compare Source

Minor Changes

#4644 cc5517ff6880bb630f1b201930acc20dd1a0b451 Thanks @lukaisailovic! - Updated @walletconnect/etherereum-provider to 2.20.0.

`v5.7.13`

Compare Source

Patch Changes

#4622 88427b2bcd13ec375ef519e9ad1ccffef9f02a7b Thanks @dan1kov! - Added rdns property to Coinbase Wallet v3 connector
#4605 3f8b2edc4f237cccff1009bcef03d51ca27a7324 Thanks @chybisov! - Bumped @safe-global/safe-apps-provider version to 0.18.6.
Updated dependencies [799ee4d4b23c2ecd64e3f3668e67634e81939719]:
- @wagmi/core@2.17.0

`v5.7.12`

Compare Source

Patch Changes

#4608 b59c024b23c69f5459b17390531207cfdf126ce4 Thanks @jxom! - Updated @walletconnect/ethereum-provider.

`v5.7.11`

Compare Source

Patch Changes

Updated dependencies [a4bd0623eed28e3761a27295831a60ad835f0ee0]:
- @wagmi/core@2.16.7

`v5.7.10`

Compare Source

Patch Changes

#4573 e944812ebc234a72c1417b77cff341166f5e0fef Thanks @ganchoradkov! - updated @walletconnect/ethereum-provider to 2.19.1
Updated dependencies [edf47477b2f6385a1c3ae01d36a8498c47f30a0b]:
- @wagmi/core@2.16.6

`v5.7.9`

Compare Source

Patch Changes

#4571 5b7101fddb61df56e34b2e02b46bc409e496eaf9 Thanks @ganchoradkov! - Updated @walletconnect/ethereum-provider to 2.19.0

`v5.7.8`

Compare Source

Patch Changes

Updated dependencies [d0c9a86921a4e939373cc6e763284e53f2a2e93c]:
- @wagmi/core@2.16.5

`v5.7.7`

Compare Source

Patch Changes

507f864d91238bfd423d0e36d3619eb9f6e52eec Thanks @jxom! - Updated @coinbase/wallet-sdk.
Updated dependencies [507f864d91238bfd423d0e36d3619eb9f6e52eec]:
- @wagmi/core@2.16.4

`v5.7.6`

Compare Source

Patch Changes

#4524 639952c97f0fe3927106f42d3c9f7f366cdf7f7a Thanks @chakra-guy! - Updated MetaMask SDK.
#4525 5aa2c095f7bfb6dfcf91c6945c3e1f9c9dd05766 Thanks @EdouardBougon! - Added Phantom flag to Injected Connector.

`v5.7.5`

Compare Source

Patch Changes

#4512 a257e8d4f97431a4af872cda1817b4ae17c7bbed Thanks @EdouardBougon! - Fixed MetaMask switchChain/addChain handling.

`v5.7.4`

Compare Source

Patch Changes

#4505 c8a257e0f6d2ece013b873895c35769a8a804fdc Thanks @chakra-guy! - Bumped Metamask SDK Version (changes include bug fixes and minor changes).

`v5.7.3`

Compare Source

Patch Changes

#4480 384a1d91597622eb59e1c05dc13ce25017c5b6d8 Thanks @RodeRickIsWatching! - Fixed invocation of default storage.
Updated dependencies [384a1d91597622eb59e1c05dc13ce25017c5b6d8]:
- @wagmi/core@2.16.3

`v5.7.2`

Compare Source

Patch Changes

012907032b532a438fce48f407470250cbc8f0c6 Thanks @jxom! - Fixed assignment in getDefaultStorage.
Updated dependencies [012907032b532a438fce48f407470250cbc8f0c6]:
- @wagmi/core@2.16.2

`v5.7.1`

Compare Source

Patch Changes

#4622 88427b2bcd13ec375ef519e9ad1ccffef9f02a7b Thanks @dan1kov! - Added rdns property to Coinbase Wallet v3 connector
#4605 3f8b2edc4f237cccff1009bcef03d51ca27a7324 Thanks @chybisov! - Bumped @safe-global/safe-apps-provider version to 0.18.6.
Updated dependencies [799ee4d4b23c2ecd64e3f3668e67634e81939719]:
- @wagmi/core@2.17.0

`v5.7.0`

Compare Source

Minor Changes

#4440 e3f63a02c1f7d80481804584f262bc98dab0400d Thanks @johanneskares! - Added Coinbase Smart Wallet "Instant Onboarding" mode to coinbaseWallet.

`v5.6.2`

Compare Source

Patch Changes

#4437 adf2253b10c6d4fc583e4bc9f01a8ef5ca267c85 Thanks @chybisov! - Bumped @safe-global/safe-apps-provider version to 0.18.5.

`v5.6.1`

Compare Source

Patch Changes

#4458 987404f590c1d29ebb3cb68928f5e54aa032793d Thanks @EdouardBougon! - Fixed MetaMask internal metadata handling.

`v5.6.0`

Compare Source

Minor Changes

#4453 070e48480194c8d7f45bda1d7dd1346e6f5d7227 Thanks @tmm! - Added narrowing to config.connectors.

Patch Changes

#4456 8b0726c1106fce88b782e676498eabf0718b2619 Thanks @EdouardBougon! - Bumped MetaMask SDK and fixed internal metadata handling.
Updated dependencies [afea6b67822a7a2b96901ec851441d27ee0f7a52, 070e48480194c8d7f45bda1d7dd1346e6f5d7227]:
- @wagmi/core@2.16.0

`v5.5.3`

Compare Source

Patch Changes

#4433 06e186cd679b27fe195309110e766fcf46d4efbc Thanks @Aerilym! - Bumped Metamask SDK version to 0.31.1.
Updated dependencies [06e186cd679b27fe195309110e766fcf46d4efbc]:
- @wagmi/core@2.15.2

`v5.5.2`

Compare Source

Patch Changes

#4422 e563ef69130a511fd6f3f72ed4cd4fbe1390541f Thanks @abretonc7s! - Bumped MetaMask SDK.

`v5.5.0`

Compare Source

Minor Changes

#4417 42e65ea4fea99c639817088bba915e0933d17141 Thanks @jxom! - Removed simulation in writeContract & sendTransaction.

Patch Changes

Updated dependencies [42e65ea4fea99c639817088bba915e0933d17141]:
- @wagmi/core@2.15.0

`v5.4.0`

Compare Source

Minor Changes

#4409 7ca62b44cd997d48f92c2b81343726a5908aa00b Thanks @fan-zhang-sv! - Added preference object for Coinbase Wallet connector.

`v5.3.10`

Compare Source

Patch Changes

#4406 a13aa8d7c38eb3cc8171a02d6302e6d12cf6bcb3 Thanks @tmm! - Added additional RDNS to MetaMask Connector.
Updated dependencies [a13aa8d7c38eb3cc8171a02d6302e6d12cf6bcb3]:
- @wagmi/core@2.14.6

`v5.3.9`

Compare Source

Patch Changes

b12a04eeec985c48d2feac94b011d41fb29ca23e Thanks @tmm! - Bumped Coinbase Wallet SDK version.

`v5.3.8`

Compare Source

Patch Changes

#4390 dac62dc99a0679fa632a0fae49873d6053d06b35 Thanks @chybisov! - Bumped Safe Apps Provider version.
Updated dependencies [6b9bbacdc7bffd44fc2165362a5e65fd434e7646]:
- @wagmi/core@2.14.5

`v5.3.7`

Compare Source

Patch Changes

Updated dependencies [e08681c81fbdf475213e2d0f4c5517d0abf4e743]:
- @wagmi/core@2.14.4

`v5.3.6`

Compare Source

Patch Changes

#4385 7558ff3133c11bc4c49473d08ee9a47eaa12df5b Thanks @cb-jake! - Bumped Coinbase Wallet SDK version.

`v5.3.5`

Compare Source

Patch Changes

7fe78f2d09778fc01fd0cffe85ba198e64999275 Thanks @tmm! - Fixed MetaMask connector not returning provider in some cases.
Updated dependencies [cb7dd2ebb871d0be8f1a11a8cd8ce592cd74b7c7]:
- @wagmi/core@2.14.3

`v5.3.4`

Compare Source

Patch Changes

#4371 b6861a4c378dab78d8751ae0ac2aa425f3c24b8f Thanks @iceanddust! - Fixed Safe connector not working in some Vite apps
Updated dependencies [d0d0963bb5904a15cf0355862d62dd141ce0c31c, ecac0ba36243d94c9199d0bd21937104c835d9a0]:
- @wagmi/core@2.14.2

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

socket-security · 2024-11-11T02:02:53Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Quality	Maintenance
eslint-config-next@15.5.2
class-variance-authority@0.7.1
@wagmi/connectors@5.3.3 ⏵ 5.9.9	⁺¹	⁺¹
tailwindcss-animate@1.0.7
wagmi@2.12.25
encoding@0.1.13
clsx@2.1.1
autoprefixer@10.4.21
postcss@8.5.6
next@15.5.2
react@18.3.1
tailwind-merge@2.6.0
tailwindcss@3.4.17
lucide-react@0.454.0
pino-pretty@11.3.0
react-dom@18.3.1
eslint@9.34.0
viem@2.21.34

View full report

socket-security · 2024-11-11T02:02:54Z

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Block		`[email protected]` has Telemetry. Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information From: packages/react-app/package.json → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is telemetry? 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 `[email protected]`. Suggestion: Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. 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.
Block		`[email protected]` has Native code. Location: Package overview From: `?` → `npm/[email protected]` → `npm/[email protected]` → `npm/@wagmi/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| Why is native code a concern? 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 `[email protected]`. Suggestion: Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. 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.
Block		`[email protected]` has Native code. Location: Package overview From: `?` → `npm/[email protected]` → `npm/[email protected]` → `npm/@wagmi/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| Why is native code a concern? 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 `[email protected]`. Suggestion: Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. 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.
Block		`[email protected]` is a AI-detected potential code anomaly. Notes: This command is typically benign and used to compile native addons. However, because it builds and may execute native code, it poses greater risk than pure-JS installs: malicious or vulnerable native source could introduce privilege-escalation, arbitrary code execution, or other system-level impacts. Review the native source, build scripts, and any downloaded prebuilt binaries before trusting the package. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` → `npm/@wagmi/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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 `[email protected]`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. 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.
Block		`[email protected]` is a AI-detected potential code anomaly. Notes: The fragment represents a sophisticated Edge VM sandbox aimed at running untrusted code with controlled IO. While not overtly malicious, its capability to patch native constructors, generate and evaluate runtime code, and route network-like fetch events through sandboxed listeners creates meaningful security risks if misused or insufficiently isolated. This warrants thorough threat modeling, strict supply-chain controls, and explicit isolation guarantees in the hosting environment before deploying in production. Confidence: 1.00 Severity: 0.60 From: packages/react-app/package.json → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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 `[email protected]`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. 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.
Block		`[email protected]` is a AI-detected potential code anomaly. Notes: This command is typically benign and used to compile native addons. However, because it builds and may execute native code, it poses greater risk than pure-JS installs: malicious or vulnerable native source could introduce privilege-escalation, arbitrary code execution, or other system-level impacts. Review the native source, build scripts, and any downloaded prebuilt binaries before trusting the package. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/[email protected]` → `npm/[email protected]` → `npm/@wagmi/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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 `[email protected]`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. 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.
Block		`[email protected]` is a AI-detected potential code anomaly. Notes: The code implements a cross-chain deposit flow with proper validations, artifact reads, and on-chain interactions. There is no evidence of hidden backdoors, data exfiltration, or malware. The main security considerations relate to token approval logic and correct configuration of flags to avoid granting excessive allowances. Overall, the module appears legitimate for a bridge deposit flow, with moderate risk primarily around configuration of approvals and correct handling of gas/fees. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/@wagmi/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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 `[email protected]`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. 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

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 063bab5 to afc428b Compare November 14, 2024 19:55

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.3.7~~ fix(deps): update dependency @wagmi/connectors to v5.3.8 Nov 14, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from afc428b to fff787f Compare November 16, 2024 01:48

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.3.8~~ fix(deps): update dependency @wagmi/connectors to v5.3.9 Nov 16, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from fff787f to ee49226 Compare November 17, 2024 06:33

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.3.9~~ fix(deps): update dependency @wagmi/connectors to v5.3.10 Nov 17, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from ee49226 to b7a0f1f Compare November 18, 2024 19:02

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.3.10~~ fix(deps): update dependency @wagmi/connectors to v5.4.0 Nov 18, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from b7a0f1f to c88a8ec Compare November 23, 2024 22:45

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.4.0~~ fix(deps): update dependency @wagmi/connectors to v5.5.0 Nov 23, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from c88a8ec to 4535d4b Compare November 30, 2024 22:53

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.5.0~~ fix(deps): update dependency @wagmi/connectors to v5.5.2 Nov 30, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 4535d4b to d398c0d Compare December 5, 2024 06:12

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.5.2~~ fix(deps): update dependency @wagmi/connectors to v5.5.3 Dec 5, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from d398c0d to 0a0beeb Compare December 15, 2024 09:09

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.5.3~~ fix(deps): update dependency @wagmi/connectors to v5.6.0 Dec 15, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 0a0beeb to 32e92e9 Compare December 15, 2024 15:33

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.6.0~~ fix(deps): update dependency @wagmi/connectors to v5.6.1 Dec 15, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 32e92e9 to 0a82aba Compare December 19, 2024 22:33

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.6.1~~ fix(deps): update dependency @wagmi/connectors to v5.6.2 Dec 19, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 0a82aba to 41bf8ad Compare December 20, 2024 02:04

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.6.2~~ fix(deps): update dependency @wagmi/connectors to v5.7.0 Dec 20, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 41bf8ad to 3844a84 Compare December 24, 2024 01:43

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.7.0~~ fix(deps): update dependency @wagmi/connectors to v5.7.1 Dec 24, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 3844a84 to 34884b1 Compare December 26, 2024 20:21

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.7.1~~ fix(deps): update dependency @wagmi/connectors to v5.7.2 Dec 26, 2024

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 34884b1 to 395250c Compare December 27, 2024 09:11

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.7.2~~ fix(deps): update dependency @wagmi/connectors to v5.7.3 Dec 27, 2024

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.8.5~~ fix(deps): update dependency @wagmi/connectors to v5.8.6 Jul 19, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from f6f956a to 877d76e Compare July 22, 2025 19:14

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.8.6~~ fix(deps): update dependency @wagmi/connectors to v5.9.0 Jul 22, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 877d76e to 8bc0992 Compare August 3, 2025 19:15

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.9.0~~ fix(deps): update dependency @wagmi/connectors to v5.9.1 Aug 3, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 8bc0992 to e3b203b Compare August 11, 2025 23:08

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.9.1~~ fix(deps): update dependency @wagmi/connectors to v5.9.2 Aug 11, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from e3b203b to 924b2c6 Compare August 14, 2025 23:07

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.9.2~~ fix(deps): update dependency @wagmi/connectors to v5.9.3 Aug 14, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 924b2c6 to bab8677 Compare August 21, 2025 20:26

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.9.3~~ fix(deps): update dependency @wagmi/connectors to v5.9.4 Aug 21, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from bab8677 to 752c605 Compare August 27, 2025 18:42

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.9.4~~ fix(deps): update dependency @wagmi/connectors to v5.9.5 Aug 27, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 752c605 to 8686bff Compare August 31, 2025 12:03

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.9.5~~ fix(deps): update dependency @wagmi/connectors to v5.9.8 Aug 31, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 8686bff to 152e66c Compare September 2, 2025 01:33

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.9.8~~ fix(deps): update dependency @wagmi/connectors to v5.9.9 Sep 2, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 152e66c to e013a9f Compare September 20, 2025 21:49

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.9.9~~ fix(deps): update dependency @wagmi/connectors to v5.10.0 Sep 20, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from e013a9f to 5bc5edc Compare September 22, 2025 19:33

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.10.0~~ fix(deps): update dependency @wagmi/connectors to v5.10.1 Sep 22, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 5bc5edc to a31090f Compare September 25, 2025 17:45

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.10.1~~ fix(deps): update dependency @wagmi/connectors to v5.10.2 Sep 25, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from a31090f to ab410aa Compare September 28, 2025 02:46

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.10.2~~ fix(deps): update dependency @wagmi/connectors to v5.11.0 Sep 28, 2025

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from ab410aa to 8b299ed Compare September 28, 2025 06:15

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.11.0~~ fix(deps): update dependency @wagmi/connectors to v5.11.1 Sep 28, 2025

fix(deps): update dependency @wagmi/connectors to v5.11.2

7b168c4

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate bot force-pushed the renovate/wagmi-connectors-5.x branch from 8b299ed to 7b168c4 Compare September 28, 2025 22:44

renovate bot changed the title ~~fix(deps): update dependency @wagmi/connectors to v5.11.1~~ fix(deps): update dependency @wagmi/connectors to v5.11.2 Sep 28, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update dependency @wagmi/connectors to v5.11.2 #36

fix(deps): update dependency @wagmi/connectors to v5.11.2 #36

Uh oh!

renovate bot commented Nov 11, 2024 •

edited

Loading

Uh oh!

socket-security bot commented Nov 11, 2024 •

edited

Loading

Uh oh!

socket-security bot commented Nov 11, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

fix(deps): update dependency @wagmi/connectors to v5.11.2 #36

Are you sure you want to change the base?

fix(deps): update dependency @wagmi/connectors to v5.11.2 #36

Uh oh!

Conversation

renovate bot commented Nov 11, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

socket-security bot commented Nov 11, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Nov 11, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Nov 11, 2024 •

edited

Loading

socket-security bot commented Nov 11, 2024 •

edited

Loading

socket-security bot commented Nov 11, 2024 •

edited

Loading