Skip to content

Conversation

joaquim-verges
Copy link
Member

@joaquim-verges joaquim-verges commented Sep 22, 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

[email protected]

Minor Changes

Patch Changes

  • #8100 a94f229 Thanks @MananTank! - Update the onSuccess, onError, and onCancel callback props of the BuyWidget to be called with the quote object

    <BuyWidget
      onSuccess={(quote) => console.log("Swap completed:", quote)}
      onError={(error, quote) => console.error("Swap failed:", error, quote)}
      onCancel={(quote) => console.log("Swap cancelled:", quote)}
    />

@thirdweb-dev/[email protected]

Patch Changes

@thirdweb-dev/[email protected]


PR-Codex overview

This PR focuses on updating the version numbers of various packages and their changelogs, reflecting new releases and changes made in the codebase.

Detailed summary

  • Updated version in packages/thirdweb/package.json from 5.107.1 to 5.108.0
  • Updated version in packages/nebula/package.json from 0.2.52 to 0.2.53
  • Updated version in packages/wagmi-adapter/package.json from 0.2.149 to 0.2.150
  • Added changelog entries for 0.2.53 in packages/nebula/CHANGELOG.md
  • Added changelog entries for 5.108.0 in packages/thirdweb/CHANGELOG.md including:
    • New verifyPayment() backend utility for x402 payments
    • Updated callback props for the BuyWidget component

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

Summary by CodeRabbit

  • New Features

    • BuyWidget callbacks now receive a quote object; onError includes both error and quote.
    • x402 payments support arbitrary chain IDs via a backend verification utility.
  • Documentation

    • Updated changelogs to reflect new versions and API updates.
  • Chores

    • Version bumps: thirdweb to 5.108.0, nebula to 0.2.53, wagmi-adapter to 0.2.150.
    • Dependency updates aligned with the latest thirdweb release.

@joaquim-verges joaquim-verges requested review from a team as code owners September 22, 2025 22:36
Copy link

vercel bot commented Sep 22, 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 Sep 23, 2025 0:11am
nebula Ready Ready Preview Comment Sep 23, 2025 0:11am
thirdweb_playground Ready Ready Preview Comment Sep 23, 2025 0:11am
thirdweb-www Error Error Sep 23, 2025 0:11am
wallet-ui Ready Ready Preview Comment Sep 23, 2025 0:11am

Copy link
Contributor

coderabbitai bot commented Sep 22, 2025

Walkthrough

Removes a changeset entry and bumps versions across packages. Updates changelogs for nebula (0.2.53), thirdweb (5.108.0), and wagmi-adapter (0.2.150). No code or public API changes; all edits are metadata and documentation.

Changes

Cohort / File(s) Summary of Changes
Remove changeset entry
\.changeset/some-moons-burn.md
Deleted changeset that previously indicated a minor bump and changelog note for thirdweb.
Nebula release metadata
packages/nebula/CHANGELOG.md, packages/nebula/package.json
Added changelog entry for 0.2.53 noting dependency update to [email protected]; bumped version 0.2.52 → 0.2.53.
thirdweb release metadata
packages/thirdweb/CHANGELOG.md, packages/thirdweb/package.json
Added changelog for 5.108.0 documenting minor/patch notes (including BuyWidget callback signature note in changelog); bumped version 5.107.1 → 5.108.0.
wagmi-adapter release metadata
packages/wagmi-adapter/CHANGELOG.md, packages/wagmi-adapter/package.json
Added changelog header for 0.2.150; bumped version 0.2.149 → 0.2.150.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

packages, SDK

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The PR description includes autogenerated release notes and changelog entries that document the package bumps and noted API changes, but it does not follow the repository's PR template: it lacks the explicit "Notes for the reviewer" and "How to test" sections and does not include an issue/Linear tag or the recommended title format. Because those template sections are missing, reviewers lack guidance on testing steps or any reviewer-specific context beyond the changelog. Therefore the description does not meet the repository's required template expectations. Please update the PR description to include a short "Notes for the reviewer" summarizing scope and risk and a "How to test" section with manual or automated verification steps (or explicitly state "no testing required" for a release-only changeset), and add the issue/Linear tag if applicable. Once those sections are added and the header follows the repository template, re-evaluate the description check.
Title Check ❓ Inconclusive The PR title "Version Packages" is related to the changes (this is a release/version-bump PR) but is overly generic and does not clearly communicate the primary impact or notable change (for example, [email protected] and its BuyWidget callback API update). A teammate scanning history would not know the main scope or risk from this title alone. For these reasons the title is inconclusive against the repository's title guidance. Update the title to follow the repo format and concisely summarize the primary change, for example "[SDK] Release: [email protected] — BuyWidget callback API update" or a concise aggregated release title like "[Packages] Release: [email protected], [email protected], [email protected]". After updating, re-run or request a re-check.
✅ Passed checks (1 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch changeset-release/main

📜 Recent 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 0293b67 and 5bd5bf9.

📒 Files selected for processing (7)
  • .changeset/some-moons-burn.md (0 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/some-moons-burn.md
✅ Files skipped from review due to trivial changes (1)
  • packages/nebula/package.json
🚧 Files skipped from review as they are similar to previous changes (5)
  • packages/thirdweb/package.json
  • packages/wagmi-adapter/package.json
  • packages/thirdweb/CHANGELOG.md
  • packages/wagmi-adapter/CHANGELOG.md
  • packages/nebula/CHANGELOG.md
⏰ 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). (4)
  • GitHub Check: Lint Packages
  • GitHub Check: Size
  • GitHub Check: Unit Tests
  • GitHub Check: Analyze (javascript)

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

@github-actions github-actions bot added the SDK Involves changes to the thirdweb SDK label Sep 22, 2025
Copy link
Contributor

graphite-app bot commented Sep 22, 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.

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: 1

🧹 Nitpick comments (2)
packages/wagmi-adapter/CHANGELOG.md (1)

3-4: Add a one‑liner to avoid an empty section.

Recommend noting “Version bump only; no user‑facing changes” for 0.2.150.

 ## 0.2.150
+
+- Internal: version bump only (no user-facing changes)
packages/thirdweb/CHANGELOG.md (1)

3-8: Polish changelog phrasing + inline code formatting

Recommend using backticks for the function name and “IDs” capitalization for consistency with prior entries.

- - [#8091](https://github.com/thirdweb-dev/js/pull/8091) [`5249cb7`](https://github.com/thirdweb-dev/js/commit/5249cb7409a8486346fe428f824c81dd90845555) Thanks [@joaquim-verges](https://github.com/joaquim-verges)! - Accept arbitrary chain ids for x402 payments with new verifyPayment() backend utility
+ - [#8091](https://github.com/thirdweb-dev/js/pull/8091) [`5249cb7`](https://github.com/thirdweb-dev/js/commit/5249cb7409a8486346fe428f824c81dd90845555) Thanks [@joaquim-verges](https://github.com/joaquim-verges)! - Accept arbitrary chain IDs for x402 payments via new `verifyPayment()` backend utility

Please confirm verifyPayment() is exported in [email protected]’s public API and covered in docs, matching the Minor bump rationale.

📜 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 5249cb7 and 0293b67.

📒 Files selected for processing (7)
  • .changeset/some-moons-burn.md (0 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/some-moons-burn.md
🧰 Additional context used
📓 Path-based instructions (2)
packages/wagmi-adapter/**

📄 CodeRabbit inference engine (CLAUDE.md)

Wagmi ecosystem integration is in packages/wagmi-adapter/

Files:

  • packages/wagmi-adapter/package.json
  • packages/wagmi-adapter/CHANGELOG.md
**/package.json

📄 CodeRabbit inference engine (AGENTS.md)

Track bundle budgets via package.json#size-limit

Files:

  • packages/wagmi-adapter/package.json
  • packages/thirdweb/package.json
  • packages/nebula/package.json
🧠 Learnings (2)
📓 Common learnings
Learnt from: CR
PR: thirdweb-dev/js#0
File: AGENTS.md:0-0
Timestamp: 2025-08-29T15:37:38.513Z
Learning: Applies to .changeset/*.md : Version bump rules: patch for non‑API changes; minor for new/modified public API
Learnt from: CR
PR: thirdweb-dev/js#0
File: AGENTS.md:0-0
Timestamp: 2025-08-29T15:37:38.513Z
Learning: Applies to .changeset/*.md : Each change in `packages/*` must include a changeset for the appropriate package
📚 Learning: 2025-07-18T19:19:55.613Z
Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T19:19:55.613Z
Learning: Applies to packages/wagmi-adapter/** : Wagmi ecosystem integration is in `packages/wagmi-adapter/`

Applied to files:

  • packages/wagmi-adapter/package.json
  • packages/wagmi-adapter/CHANGELOG.md
⏰ 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: Unit Tests
  • GitHub Check: Lint Packages
  • GitHub Check: Size
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Build Packages
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (3)
packages/nebula/CHANGELOG.md (1)

3-9: Changelog entry reads well.

Notes the dependency update to [email protected] with commit reference. Nothing else needed.

packages/nebula/package.json (1)

60-60: LGTM — confirm workspace dep resolves to [email protected] on publish.

packages/nebula/package.json uses "thirdweb": "workspace:". Confirm a local workspace package named "thirdweb" exists at version 5.108.0 or that Changesets/pnpm will replace "workspace:" with 5.108.0 in the published tarball; repo search failed to locate a local "thirdweb" package (script error).

packages/thirdweb/package.json (1)

430-430: Approve: semver bump to 5.108.0 — changelog present; add size‑limit config

  • Confirmed: packages/thirdweb/CHANGELOG.md contains "## 5.108.0".
  • packages/thirdweb/package.json: version bumped; no top‑level "size-limit" config found. devDependency "size-limit" = 11.2.0 and scripts.size = "size-limit". Root package.json also has no top‑level "size-limit".
  • Action: add a "size-limit" config at packages/thirdweb or at the repo root to track bundle budgets.

"types": "./dist/types/exports/thirdweb.d.ts",
"typings": "./dist/types/exports/thirdweb.d.ts",
"version": "0.2.149"
"version": "0.2.150"
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

🧩 Analysis chain

LGTM on version bump; double‑check bundle budget tracking.

Version 0.2.150 is fine; peer range thirdweb: ^5.85.0 already covers 5.108.0. Please verify you’re still tracking bundle budgets via package.json#size-limit for this package (required by guidelines). If missing by design, ignore.


🏁 Script executed:

#!/bin/bash
# Check for size-limit config in updated manifests
rg -n '"size-limit"' packages/wagmi-adapter/package.json packages/nebula/package.json || echo "No size-limit key found in these manifests"
# Sanity: show current thirdweb peer range
jq -r '.peerDependencies.thirdweb' packages/wagmi-adapter/package.json

Length of output: 50


Add missing size-limit entry to packages/wagmi-adapter/package.json

Version bump to 0.2.150 is fine; packages/wagmi-adapter/package.json currently has no "size-limit" entry — add a size-limit budget per repo guidelines or confirm intentional omission.

🤖 Prompt for AI Agents
In packages/wagmi-adapter/package.json around line 58, the version bump to
0.2.150 is present but the file is missing a "size-limit" entry; add a
"size-limit" property to the package.json (matching the repository's size-limit
format and budget used by sibling packages) with the appropriate path(s) and
size budget(s) per repo guidelines, or if omission is intentional add a brief
comment in the PR confirming the deliberate exclusion and referencing the
guideline decision.

Copy link
Contributor

github-actions bot commented Sep 22, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 64.07 KB (0%) 1.3 s (0%) 131 ms (+121.15% 🔺) 1.5 s
thirdweb (cjs) 361.6 KB (0%) 7.3 s (0%) 497 ms (-2.15% 🔽) 7.8 s
thirdweb (minimal + tree-shaking) 5.73 KB (0%) 115 ms (0%) 54 ms (+2180.52% 🔺) 168 ms
thirdweb/chains (tree-shaking) 526 B (0%) 11 ms (0%) 30 ms (+2156.13% 🔺) 40 ms
thirdweb/react (minimal + tree-shaking) 19.14 KB (0%) 383 ms (0%) 52 ms (+1721.52% 🔺) 435 ms

Copy link

codecov bot commented Sep 22, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.32%. Comparing base (a94f229) to head (5bd5bf9).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8102   +/-   ##
=======================================
  Coverage   56.32%   56.32%           
=======================================
  Files         906      906           
  Lines       59197    59197           
  Branches     4176     4176           
=======================================
  Hits        33345    33345           
  Misses      25746    25746           
  Partials      106      106           
Flag Coverage Δ
packages 56.32% <ø> (ø)
🚀 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.

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