Skip to content

Update thirdweb to 5.105.42 #914

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

Merged
merged 1 commit into from
Sep 9, 2025
Merged

Update thirdweb to 5.105.42 #914

Show file tree
Hide file tree
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 package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
"prisma": "^5.14.0",
"prom-client": "^15.1.3",
"superjson": "^2.2.1",
"thirdweb": "^5.100.1",
"thirdweb": "^5.105.42",
Copy link

@coderabbitai coderabbitai bot Sep 9, 2025

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Ensure viem/ethers compatibility and single-version dedupe.

thirdweb v5 works with viem and ethers; we already pin viem 2.22.17 in deps and resolutions and ethers v5. Confirm there’s no duplicate viem/ethers trees after the bump. (portal.thirdweb.com, github.com)

🏁 Script executed:

#!/bin/bash
# Explain dependency graph for potential duplicates
yarn why thirdweb viem ethers || true
# List any nested viem/ethers under thirdweb
fd -H node_modules | rg -nP '/(thirdweb|@thirdweb-dev)/' -n -C0 | rg -nP '/(viem|ethers)(/|@)' -n -C0 || true

Length of output: 142

🏁 Script executed:

#!/bin/bash
# Show why each package is installed
printf "\n=== yarn why thirdweb ===\n"
yarn why thirdweb || true

printf "\n=== yarn why viem ===\n"
yarn why viem || true

printf "\n=== yarn why ethers ===\n"
yarn why ethers || true

# List all installed versions of viem and ethers
printf "\n=== yarn list --pattern viem ===\n"
yarn list --pattern "viem" || true

printf "\n=== yarn list --pattern ethers ===\n"
yarn list --pattern "ethers" || true

# Find any nested viem/ethers module directories under node_modules
printf "\n=== Duplicate module directories ===\n"
find node_modules -type d | grep -E "/node_modules/(viem|ethers)$" || printf "No duplicate module dirs found\n"

Length of output: 18042

Pin ethers to a single version via resolutions
Detected two ethers versions (5.7.2 at root vs. 5.5.1 under ethers-gcp-kms-signer). Add a resolutions override in package.json (e.g. "ethers": "5.7.2") and reinstall to force-dedupe.

🤖 Prompt for AI Agents 
In package.json around line 72, multiple versions of ethers were detected (root
5.7.2 vs 5.5.1 under ethers-gcp-kms-signer); add a resolutions override to force
a single version (for example add a top-level "resolutions": { "ethers": "5.7.2"
}) and then reinstall and regenerate the lockfile (npm/yarn/pnpm install or yarn
install --check-files / yarn-deduplicate as appropriate) so the dependency is
deduped to the pinned version; if using npm, add an "overrides" entry instead of
"resolutions" with the same key/value and update the lockfile.

"undici": "^6.20.1",
"uuid": "^9.0.1",
"viem": "2.22.17",
Expand Down
Loading
Loading