Skip to content

Conversation

@joaquim-verges
Copy link
Member

@joaquim-verges joaquim-verges commented Oct 17, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@thirdweb-dev/api@0.1.0

Minor Changes

@thirdweb-dev/nebula@0.2.70

Patch Changes

thirdweb@5.109.1

Patch Changes

@thirdweb-dev/wagmi-adapter@0.2.167

wagmi-inapp@0.0.12

Patch Changes

  • Updated dependencies [5ff6063, 72fbb15]:
    • thirdweb@5.109.1
    • @thirdweb-dev/wagmi-adapter@0.2.167

PR-Codex overview

This PR focuses on updating version numbers across various packages, along with significant changes in the CHANGELOG.md files for those packages, reflecting new features and updates.

Detailed summary

  • Deleted three .md files in .changeset.
  • Updated version to 5.109.1 in packages/thirdweb/package.json.
  • Updated version to 0.0.12 in apps/wagmi-demo/package.json.
  • Updated version to 0.2.70 in packages/nebula/package.json.
  • Updated version to 0.2.167 in packages/wagmi-adapter/package.json.
  • Updated version to 0.1.0 in packages/api/package.json.
  • Added changelog entries for 0.1.0 in packages/api/CHANGELOG.md.
  • Added changelog entries for 0.2.70 in packages/nebula/CHANGELOG.md.
  • Added changelog entries for 0.0.12 in apps/wagmi-demo/CHANGELOG.md.
  • Added changelog entries for 5.109.1 in packages/thirdweb/CHANGELOG.md.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • New Features

    • Token search input now autofocuses when opening the token selector modal in Buy, Swap, and Bridge widgets
    • TokenIcon now resolves automatically when available
  • Chores

    • Version updates across multiple packages (thirdweb, wagmi-adapter, wagmi-demo, nebula, and api packages)

@joaquim-verges joaquim-verges requested review from a team as code owners October 17, 2025 14:50
@vercel
Copy link

vercel bot commented Oct 17, 2025

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

Project Deployment Preview Comments Updated (UTC)
docs-v2 Ready Ready Preview Comment Oct 20, 2025 2:01am
nebula Ready Ready Preview Comment Oct 20, 2025 2:01am
thirdweb_playground Ready Ready Preview Comment Oct 20, 2025 2:01am
thirdweb-www Ready Ready Preview Comment Oct 20, 2025 2:01am
wallet-ui Ready Ready Preview Comment Oct 20, 2025 2:01am

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

@graphite-app
Copy link
Contributor

graphite-app bot commented Oct 17, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@github-actions github-actions bot added packages SDK Involves changes to the thirdweb SDK labels Oct 17, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 17, 2025

Walkthrough

Removed a changeset file and applied patch version bumps and changelog entries across four packages (apps/wagmi-demo, packages/nebula, packages/thirdweb, packages/wagmi-adapter), with changelogs noting dependency updates and a token-selector autofocus fix in thirdweb's changelog.

Changes

Cohort / File(s) Summary
Changeset removal
.changeset/happy-trees-doubt.md
Removed changeset entry that documented the token selector autofocus patch
Wagmi demo version & changelog
apps/wagmi-demo/package.json, apps/wagmi-demo/CHANGELOG.md
Bumped version 0.0.11 → 0.0.12; added changelog entry referencing dependency updates to thirdweb@5.109.1 and @thirdweb-dev/wagmi-adapter@0.2.167
Nebula version & changelog
packages/nebula/package.json, packages/nebula/CHANGELOG.md
Bumped version 0.2.69 → 0.2.70; added changelog entry referencing dependency update to thirdweb@5.109.1
Thirdweb version & changelog
packages/thirdweb/package.json, packages/thirdweb/CHANGELOG.md
Bumped version 5.109.0 → 5.109.1; added changelog entry noting autofocus fix for token search input when opening token selector modal in BuyWidget, SwapWidget, and BridgeWidget
Wagmi adapter version & changelog
packages/wagmi-adapter/package.json, packages/wagmi-adapter/CHANGELOG.md
Bumped version 0.2.166 → 0.2.167; inserted a new changelog header for 0.2.167 (no additional content)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The PR description does not follow the required template structure. The template specifies required sections including a title in the format "[SDK/Dashboard/Portal] Feature/Fix: Concise title", a Linear issue tag section, "Notes for the reviewer", and "How to test". The provided description appears to be auto-generated by the Changesets release action and includes a "Releases" section with version numbers and changelog details, along with a PR-Codex overview, but it lacks all four required template sections. While the description comprehensively documents what this release PR accomplishes, it does not adhere to the specified template format. The PR description should be updated to follow the required template structure. Add a proper title in the format "[SDK/Dashboard/Portal] Feature/Fix: Concise title" (e.g., "[SDK] Fix: Token selector autofocus and dependency updates"), include the Linear issue reference if applicable, add a "Notes for the reviewer" section highlighting that this is an automated release PR with package version updates, and provide a "How to test" section with relevant testing instructions. Alternatively, if automated release PRs should be exempt from the template, this should be documented in repository guidelines and the template should be updated accordingly.
Title Check ❓ Inconclusive The title "Version Packages" is vague and generic, using non-descriptive language that doesn't convey meaningful information about the changeset. While it's technically related to the PR's purpose of releasing updated versions, the title is so broad that it could apply to many different release changesets. It doesn't clearly summarize what specific changes or features are being released, making it difficult for a teammate scanning the history to understand the primary change beyond knowing that versions were updated.
✅ Passed checks (1 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch changeset-release/main

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 17, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 64.51 KB (0%) 1.3 s (0%) 202 ms (+97.42% 🔺) 1.5 s
thirdweb (cjs) 365.68 KB (0%) 7.4 s (0%) 991 ms (-0.26% 🔽) 8.4 s
thirdweb (minimal + tree-shaking) 5.73 KB (0%) 115 ms (0%) 119 ms (+2259.69% 🔺) 234 ms
thirdweb/chains (tree-shaking) 526 B (0%) 11 ms (0%) 62 ms (+2025.81% 🔺) 72 ms
thirdweb/react (minimal + tree-shaking) 19.13 KB (0%) 383 ms (0%) 82 ms (+965.74% 🔺) 464 ms

@codecov
Copy link

codecov bot commented Oct 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 54.90%. Comparing base (72fbb15) to head (bd2c110).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8272   +/-   ##
=======================================
  Coverage   54.89%   54.90%           
=======================================
  Files         919      919           
  Lines       60622    60622           
  Branches     4128     4116   -12     
=======================================
+ Hits        33276    33282    +6     
+ Misses      27246    27239    -7     
- Partials      100      101    +1     
Flag Coverage Δ
packages 54.90% <ø> (+<0.01%) ⬆️
see 2 files with indirect coverage changes
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/api/package.json (1)

1-61: Consider adding bundle size tracking via size-limit.

Per coding guidelines, packages should track bundle budgets via package.json#size-limit. This package currently lacks this field. While this is outside the scope of an automated release PR, consider adding size-limit configuration in a follow-up PR to prevent unintended bundle bloat, especially for an exported API client library.

Example addition to package.json:

  "size-limit": [
    {
      "path": "./dist/esm/exports/thirdweb.js",
      "limit": "50 KB"
    }
  ]

This ensures bundle size doesn't regress as the API evolves.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 60bb2ca and bd2c110.

📒 Files selected for processing (11)
  • .changeset/happy-trees-doubt.md (0 hunks)
  • apps/wagmi-demo/CHANGELOG.md (1 hunks)
  • apps/wagmi-demo/package.json (1 hunks)
  • packages/api/CHANGELOG.md (1 hunks)
  • packages/api/package.json (1 hunks)
  • packages/nebula/CHANGELOG.md (1 hunks)
  • packages/nebula/package.json (1 hunks)
  • packages/thirdweb/CHANGELOG.md (1 hunks)
  • packages/thirdweb/package.json (1 hunks)
  • packages/wagmi-adapter/CHANGELOG.md (1 hunks)
  • packages/wagmi-adapter/package.json (1 hunks)
💤 Files with no reviewable changes (1)
  • .changeset/happy-trees-doubt.md
✅ Files skipped from review due to trivial changes (2)
  • packages/api/CHANGELOG.md
  • packages/thirdweb/package.json
🚧 Files skipped from review as they are similar to previous changes (7)
  • apps/wagmi-demo/CHANGELOG.md
  • packages/nebula/CHANGELOG.md
  • apps/wagmi-demo/package.json
  • packages/wagmi-adapter/CHANGELOG.md
  • packages/wagmi-adapter/package.json
  • packages/thirdweb/CHANGELOG.md
  • packages/nebula/package.json
🧰 Additional context used
📓 Path-based instructions (1)
**/package.json

📄 CodeRabbit inference engine (AGENTS.md)

Track bundle budgets via package.json#size-limit

Files:

  • packages/api/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: Unit Tests
  • GitHub Check: Build Packages
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (1)
packages/api/package.json (1)

3-3: Version bump aligns with PR objectives and semantic versioning.

The version update from 0.0.3 to 0.1.0 correctly reflects a minor release, consistent with the PR objectives noting an API update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

packages SDK Involves changes to the thirdweb SDK

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant