chore: upgrade wagmi, @wagmi/core, viem #1653
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
DanielSinclair
force-pushed
the
@daniel/wagmi-v1.4.10
branch
from
b84fa80
to
1743869
Compare
magiziz
approved these changes
Dec 14, 2023
DanielSinclair
force-pushed
the
@daniel/wagmi-v1.4.10
branch
from
9374e09
to
b17425f
Compare
This was referenced Dec 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for Wagmi
1.4.12to mitigate a supply-chain attack on the@ledgerhq/connect-kitpackage. RainbowKit dApp's were not directly impacted, but dApps that used theLedgerConnectorconnector in earlier versions of Wagmi could be. Please upgrade your instances of Wagmi and RainbowKit.Changes
wagmi1.4.12viem1.19.15