Skip to content

Bump wagmi from 2.14.13 to 2.19.1 #322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

Bump wagmi from 2.14.13 to 2.19.1 #322

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
"vocs": "^1",
"typescript": "^5.5.4",
"viem": "2.x",
"wagmi": "2.x",
"wagmi": "3.x",
Copy link

@cursor cursor bot Nov 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Incompatible wagmi version with peer dependencies

The PR description states bumping wagmi from 2.14.13 to 2.19.1, but the diff changes the version from 2.x to 3.x, which is a major version upgrade with breaking changes. This creates a peer dependency conflict with @privy-io/[email protected], which explicitly requires wagmi: ^2.14.11 according to the lock file. Installing wagmi 3.x will cause peer dependency warnings or errors and likely runtime failures when using Privy integration, as the packages are incompatible.

Fix in Cursor Fix in Web

"seismic-viem": "workspace:*",
"seismic-react": "workspace:*",
"@privy-io/react-auth": "^2.6.2",
Expand Down