Skip to content

Conversation

@joaquim-verges
Copy link
Member

@joaquim-verges joaquim-verges commented Nov 24, 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@5.113.0

Minor Changes

  • #8444 9809d5c Thanks @joaquim-verges! - # New useFetchWithPayment() React Hook

    Added a new React hook that wraps the native fetch API to automatically handle 402 Payment Required responses using the x402 payment protocol.

    Features

    • Automatic Payment Handling: Automatically detects 402 responses, creates payment headers, and retries requests
    • Built-in UI: Shows an error modal with retry and fund wallet options when payment fails
    • Sign In Flow: Prompts users to connect their wallet if not connected, then automatically retries the payment
    • Insufficient Funds Flow: Integrates BuyWidget to help users top up their wallet directly in the modal
    • Customizable: Supports theming, custom payment selectors, BuyWidget customization, and ConnectModal customization
    • Opt-out Modal: Can disable the modal to handle errors manually

    Basic Usage

    The hook automatically parses JSON responses by default.

    import { useFetchWithPayment } from "thirdweb/react";
    import { createThirdwebClient } from "thirdweb";
    
    const client = createThirdwebClient({ clientId: "your-client-id" });
    
    function MyComponent() {
      const { fetchWithPayment, isPending } = useFetchWithPayment(client);
    
      const handleApiCall = async () => {
        // Response is automatically parsed as JSON by default
        const data = await fetchWithPayment(
          "https://api.example.com/paid-endpoint",
        );
        console.log(data);
      };
    
      return (
        <button onClick={handleApiCall} disabled={isPending}>
          {isPending ? "Loading..." : "Make Paid API Call"}
        </button>
      );
    }

    Customize Response Parsing

    By default, responses are parsed as JSON. You can customize this with the parseAs option:

    // Parse as text instead of JSON
    const { fetchWithPayment } = useFetchWithPayment(client, {
      parseAs: "text",
    });
    
    // Or get the raw Response object
    const { fetchWithPayment } = useFetchWithPayment(client, {
      parseAs: "raw",
    });

    Customize Theme & Payment Options

    const { fetchWithPayment } = useFetchWithPayment(client, {
      maxValue: 5000000n, // 5 USDC in base units
      theme: "light",
      paymentRequirementsSelector: (requirements) => {
        // Custom logic to select preferred payment method
        return requirements[0];
      },
    });

    Customize Fund Wallet Widget

    const { fetchWithPayment } = useFetchWithPayment(client, {
      fundWalletOptions: {
        title: "Add Funds",
        description: "You need more tokens to complete this payment",
        buttonLabel: "Get Tokens",
      },
    });

    Customize Connect Modal

    const { fetchWithPayment } = useFetchWithPayment(client, {
      connectOptions: {
        wallets: [inAppWallet(), createWallet("io.metamask")],
        title: "Sign in to continue",
        showThirdwebBranding: false,
      },
    });

    Disable Modal (Handle Errors Manually)

    const { fetchWithPayment, error } = useFetchWithPayment(client, {
      showErrorModal: false,
    });
    
    // Handle the error manually
    if (error) {
      console.error("Payment failed:", error);
    }

Patch Changes

@thirdweb-dev/nebula@0.2.94

Patch Changes

@thirdweb-dev/wagmi-adapter@0.2.191

wagmi-inapp@0.0.36

Patch Changes

  • Updated dependencies [52aba0f, 9809d5c]:
    • thirdweb@5.113.0
    • @thirdweb-dev/wagmi-adapter@0.2.191

PR-Codex overview

This PR focuses on updating version numbers across various packages and introducing a new useFetchWithPayment() React Hook in thirdweb, which enhances payment handling for API calls.

Detailed summary

  • Updated version numbers in packages/thirdweb, apps/wagmi-demo, packages/nebula, and packages/wagmi-adapter.
  • Introduced useFetchWithPayment() hook in thirdweb for automatic payment handling.
  • Added customizable options for response parsing, theme, and payment methods.
  • Included examples for basic usage and customization in documentation.

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

Summary by CodeRabbit

  • New Features

    • Added useFetchWithPayment() React Hook for automatic payment request handling with built-in UI and wallet integration.
  • Bug Fixes

    • Fixed chain switching behavior for connected wallets.
  • Chores

    • Updated thirdweb dependency to v5.113.0 across packages.
    • Bumped package versions: wagmi-demo (0.0.36), nebula (0.2.94), wagmi-adapter (0.2.191).

✏️ Tip: You can customize this high-level summary in your review settings.

@joaquim-verges joaquim-verges requested review from a team as code owners November 24, 2025 22:44
@vercel
Copy link

vercel bot commented Nov 24, 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 Nov 24, 2025 11:27pm
nebula Ready Ready Preview Comment Nov 24, 2025 11:27pm
thirdweb_playground Ready Ready Preview Comment Nov 24, 2025 11:27pm
thirdweb-www Ready Ready Preview Comment Nov 24, 2025 11:27pm
wallet-ui Ready Ready Preview Comment Nov 24, 2025 11:27pm

@graphite-app
Copy link
Contributor

graphite-app bot commented Nov 24, 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 Nov 24, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 24, 2025

Walkthrough

Version bumps and changelog updates across multiple packages; a changeset documentation file describing useFetchWithPayment() was removed. The thirdweb package version was incremented and its changelog documents a new useFetchWithPayment() hook.

Changes

Cohort / File(s) Summary
Package version bumps
apps/wagmi-demo/package.json, packages/nebula/package.json, packages/thirdweb/package.json, packages/wagmi-adapter/package.json
Updated package versions: wagmi-demo → 0.0.36, nebula → 0.2.94, thirdweb → 5.113.0, wagmi-adapter → 0.2.191.
Changelog updates
apps/wagmi-demo/CHANGELOG.md, packages/nebula/CHANGELOG.md, packages/thirdweb/CHANGELOG.md, packages/wagmi-adapter/CHANGELOG.md
Added new release entries for the bumped versions; thirdweb changelog documents a new React hook useFetchWithPayment() and a patch note.
Changeset / docs removal
.changeset/wet-maps-play.md
Deleted changeset file that described the useFetchWithPayment() hook, its features, usage examples, and customization notes.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant Client
    participant Hook as useFetchWithPayment
    participant API
    participant PaymentUI
    participant Retry

    Client->>Hook: request(url, opts)
    Hook->>API: fetch(url, opts)
    API-->>Hook: 402 Payment Required
    Hook->>PaymentUI: open payment/sign-in modal
    PaymentUI-->>Hook: payment authorized
    Hook->>Retry: attach payment headers
    Retry->>API: retry fetch with payment headers
    API-->>Client: success response
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Mostly version/changelog updates and one documentation deletion.
  • Review focus:
    • packages/thirdweb/CHANGELOG.md — confirm accuracy of the documented public API addition (useFetchWithPayment) versus actual code changes.
    • .changeset/wet-maps-play.md deletion — ensure no loss of required documentation or release notes.
    • Package.json version bumps — confirm consistency across release tooling.

Possibly related PRs

  • Version Packages #8370 — touches payment-fetch functionality (useFetchWithPayment / wrapFetchWithPayment); likely related API/validation changes.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Version Packages' accurately reflects the main objective of this release PR to version and publish updated packages.
Description check ✅ Passed The PR description comprehensively documents the release details, changelog entries, version bumps, and new features, providing clear information for reviewers and maintainers.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • 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 21106af and 39fa990.

📒 Files selected for processing (9)
  • .changeset/wet-maps-play.md (0 hunks)
  • apps/wagmi-demo/CHANGELOG.md (1 hunks)
  • apps/wagmi-demo/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/wet-maps-play.md
✅ Files skipped from review due to trivial changes (1)
  • packages/wagmi-adapter/CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes (6)
  • packages/wagmi-adapter/package.json
  • packages/thirdweb/package.json
  • packages/nebula/package.json
  • packages/nebula/CHANGELOG.md
  • packages/thirdweb/CHANGELOG.md
  • apps/wagmi-demo/package.json
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-24T22:45:01.181Z
Learning: Applies to packages/**/.changeset/*.md : Each change in packages/* should contain a changeset for the appropriate package with the appropriate version bump: patch for changes that don't impact the public API, minor for any new/modified public API
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-24T22:43:43.622Z
Learning: Run `pnpm changeset` after making changes in `packages/*` for semantic versioning
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-24T22:43:43.622Z
Learning: Use `patch` version bump for changes that don't impact the public API
📚 Learning: 2025-11-24T22:45:01.181Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-24T22:45:01.181Z
Learning: Applies to packages/**/.changeset/*.md : Each change in packages/* should contain a changeset for the appropriate package with the appropriate version bump: patch for changes that don't impact the public API, minor for any new/modified public API

Applied to files:

  • apps/wagmi-demo/CHANGELOG.md
📚 Learning: 2025-11-24T22:43:43.622Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-24T22:43:43.622Z
Learning: Use `patch` version bump for changes that don't impact the public API

Applied to files:

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

3-9: Changelog entry verified and correct.

All version numbers match:

  • Package version: 0.0.36 ✓
  • thirdweb: 5.113.0 ✓
  • @thirdweb-dev/wagmi-adapter: 0.2.191 ✓

The patch version bump is appropriate for dependency-only updates, and the changelog format is consistent with previous releases in the monorepo.


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

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 (4)
packages/thirdweb/CHANGELOG.md (4)

92-99: Add missing imports in the Connect Modal customization example.

The example uses inAppWallet() and createWallet(...) without imports. Add them to avoid confusion.

-  const { fetchWithPayment } = useFetchWithPayment(client, {
+  import { inAppWallet, createWallet } from "thirdweb/wallets";
+  const { fetchWithPayment } = useFetchWithPayment(client, {
     connectOptions: {
       wallets: [inAppWallet(), createWallet("io.metamask")],
       title: "Sign in to continue",
       showThirdwebBranding: false,
     },
   });

101-112: Clarify manual error-handling API shape.

The sample accesses error from the hook return. Please confirm the hook indeed returns { error } and, if so, briefly document the error type/shape to guide consumers (e.g., includes code, message, cause).


7-18: Add quick pointer to x402 docs and client-component note.

  • Link to x402/x-payments docs for context.
  • Mention this hook must run in a React client component (’use client’), per repo guidance for hooks.

Based on learnings, use client components for hooks.


52-62: Improve “parseAs: raw” example.

When parseAs: "raw" is used, show reading from the Response (e.g., await res.text() or res.json()), so users don’t assume it’s already parsed.

📜 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 9809d5c and 21106af.

📒 Files selected for processing (9)
  • .changeset/wet-maps-play.md (0 hunks)
  • apps/wagmi-demo/CHANGELOG.md (1 hunks)
  • apps/wagmi-demo/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/wet-maps-play.md
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{js,jsx,ts,tsx,json}

📄 CodeRabbit inference engine (AGENTS.md)

Biome governs formatting and linting; its rules live in biome.json. Run pnpm fix & pnpm lint before committing, ensure there are no linting errors

Files:

  • packages/wagmi-adapter/package.json
  • packages/thirdweb/package.json
  • packages/nebula/package.json
  • apps/wagmi-demo/package.json
packages/thirdweb/package.json

📄 CodeRabbit inference engine (CLAUDE.md)

Track bundle budgets via package.json#size-limit

Files:

  • packages/thirdweb/package.json
🧠 Learnings (9)
📓 Common learnings
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-24T22:45:01.181Z
Learning: Applies to packages/**/.changeset/*.md : Each change in packages/* should contain a changeset for the appropriate package with the appropriate version bump: patch for changes that don't impact the public API, minor for any new/modified public API
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-24T22:43:43.622Z
Learning: Run `pnpm changeset` after making changes in `packages/*` for semantic versioning
📚 Learning: 2025-11-24T22:45:01.181Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-24T22:45:01.181Z
Learning: Applies to packages/**/.changeset/*.md : Each change in packages/* should contain a changeset for the appropriate package with the appropriate version bump: patch for changes that don't impact the public API, minor for any new/modified public API

Applied to files:

  • packages/wagmi-adapter/CHANGELOG.md
  • packages/nebula/CHANGELOG.md
📚 Learning: 2025-11-24T22:43:43.622Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-24T22:43:43.622Z
Learning: Applies to packages/thirdweb/src/exports/**/*.{ts,tsx} : Export everything via `exports/` directory, grouped by feature in SDK development

Applied to files:

  • packages/wagmi-adapter/package.json
  • packages/thirdweb/package.json
  • packages/nebula/package.json
📚 Learning: 2025-11-24T22:43:43.622Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-24T22:43:43.622Z
Learning: Use `patch` version bump for changes that don't impact the public API

Applied to files:

  • packages/thirdweb/package.json
  • packages/nebula/package.json
  • packages/nebula/CHANGELOG.md
  • apps/wagmi-demo/CHANGELOG.md
📚 Learning: 2025-11-24T22:45:01.181Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-24T22:45:01.181Z
Learning: Applies to packages/thirdweb/src/exports/**/*.{ts,tsx} : Export everything in packages/thirdweb via the exports/ directory, grouped by feature. Every public symbol must have comprehensive TSDoc including at least one example block that compiles and one custom annotation (beta, internal, experimental, etc.)

Applied to files:

  • packages/nebula/package.json
📚 Learning: 2025-11-24T22:44:20.949Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-11-24T22:44:20.949Z
Learning: Use interactive client components for UI that relies on hooks (`useState`, `useEffect`, React Query, wallet hooks)

Applied to files:

  • packages/thirdweb/CHANGELOG.md
📚 Learning: 2025-11-24T22:44:20.949Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: .cursor/rules/dashboard.mdc:0-0
Timestamp: 2025-11-24T22:44:20.949Z
Learning: Use client components for anything that consumes hooks from `tanstack/react-query` or thirdweb SDKs

Applied to files:

  • packages/thirdweb/CHANGELOG.md
📚 Learning: 2025-11-24T22:43:43.622Z
Learnt from: CR
Repo: thirdweb-dev/js PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-24T22:43:43.622Z
Learning: Applies to apps/dashboard/src/**/*.{ts,tsx} : Handle interactive UI with React hooks (`useState`, `useEffect`, React Query, wallet hooks) in client components

Applied to files:

  • packages/thirdweb/CHANGELOG.md
📚 Learning: 2025-05-27T19:54:55.885Z
Learnt from: MananTank
Repo: thirdweb-dev/js PR: 7177
File: apps/dashboard/src/app/(app)/(dashboard)/(chain)/[chain_id]/[contractAddress]/public-pages/erc20/erc20.tsx:15-17
Timestamp: 2025-05-27T19:54:55.885Z
Learning: The `fetchDashboardContractMetadata` function from "3rdweb-sdk/react/hooks/useDashboardContractMetadata" has internal error handlers for all promises and cannot throw errors, so external error handling is not needed when calling this function.

Applied to files:

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

433-433: Version bump is semantically correct.

The minor version bump (5.112.4 → 5.113.0) appropriately reflects the addition of new public API (useFetchWithPayment hook) while maintaining backward compatibility.

packages/nebula/package.json (1)

60-60: Version bump is semantically correct.

The patch version bump (0.2.93 → 0.2.94) appropriately reflects dependency updates without public API changes.

apps/wagmi-demo/package.json (1)

4-4: Version bump is semantically correct.

The patch version bump (0.0.35 → 0.0.36) appropriately reflects dependency updates in the demo app.

apps/wagmi-demo/CHANGELOG.md (1)

3-9: Changelog entry is correctly formatted and documents all dependency updates.

The 0.0.36 release notes properly document the dependency bumps to thirdweb@5.113.0 and @thirdweb-dev/wagmi-adapter@0.2.191 with a commit reference.

packages/wagmi-adapter/package.json (1)

59-59: Version bump is semantically correct.

The patch version bump (0.2.190 → 0.2.191) appropriately reflects the release.

packages/nebula/CHANGELOG.md (1)

3-8: Changelog entry is correctly formatted and documents the dependency update.

The 0.2.94 release notes properly document the update to thirdweb@5.113.0 with a commit reference, following the expected changelog format for patch releases.

packages/thirdweb/CHANGELOG.md (1)

64-75: The review comment is incorrect and should be discarded.

The original review conflates two different APIs. Version 5.111.5 introduced wrapFetchWithPayment with a maxAmount parameter, while version 5.113.0 documents useFetchWithPayment (a new hook) that uses maxValue. The CHANGELOG snippet correctly uses maxValue and matches the actual UseFetchWithPaymentOptions type definition in the codebase. No changes are needed.

Likely an incorrect or invalid review comment.

Comment on lines +3 to +4
## 0.2.191

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 | 🔴 Critical

🧩 Analysis chain

Missing changelog documentation for 0.2.191 release.

The changelog entry for version 0.2.191 lacks content—it has no "### Patch Changes" section or any documentation of what changed. This is inconsistent with other entries in the file (0.2.190, 0.2.188, etc.) and with the related changelog entry in apps/wagmi-demo/CHANGELOG.md, which documents dependency updates to this package.

Either this release should have no changes (and the version should not be bumped), or the changelog must document what changed in a "### Patch Changes" section.


🏁 Script executed:

#!/bin/bash
# Verify if 0.2.191 matches 0.2.190 or if there were actual changes
# Check git history for commits between these tags
git log --oneline --grep="0.2.19" || echo "No commit history available"

# Check if packages/wagmi-adapter had source code changes
git diff HEAD~20..HEAD -- packages/wagmi-adapter/src || echo "Unable to retrieve diff"

Length of output: 3852


The script confirms actual code changes exist in packages/wagmi-adapter/src/connector.ts. Let me verify if a changeset file was created for this version bump.


---

🏁 Script executed:

```shell
#!/bin/bash
# Check for changeset files related to wagmi-adapter
find . -path "*/.changeset/*.md" -type f | head -20

# Check specifically for recent changesets in .changeset directory
if [ -d .changeset ]; then
  echo "=== Recent changeset files ==="
  ls -lt .changeset/*.md 2>/dev/null | head -10
  echo "=== Changeset content for wagmi-adapter ==="
  grep -l "wagmi-adapter" .changeset/*.md 2>/dev/null | head -5 | xargs -I {} sh -c 'echo "File: {}"; cat "{}"'
fi

Length of output: 26



---

🏁 Script executed:

```shell
#!/bin/bash
# Find all .changeset directories
find . -type d -name ".changeset" | grep -v "\.git" | head -10

# Check if wagmi-adapter has its own .changeset
ls -la packages/wagmi-adapter/.changeset/ 2>/dev/null || echo "No .changeset in wagmi-adapter"

# List actual content in root .changeset if it exists (excluding README)
if [ -d .changeset ]; then
  echo "=== Root .changeset directory contents ==="
  ls -la .changeset/ | grep -v README
fi

# Check git status for any pending changesets
git status --short 2>/dev/null | grep -i changeset || echo "No changesets in git status"

Length of output: 286


Missing changeset file and incomplete changelog documentation for 0.2.191.

Code changes exist in packages/wagmi-adapter/src/connector.ts (chain storage refactoring, imports, type casting), but no changeset file was created. This bypasses the repository's changeset workflow. The changelog entry for 0.2.191 also lacks a "### Patch Changes" section.

Required fixes:

  • Create a changeset file in .changeset/ directory documenting the changes to wagmi-adapter (patch bump appropriate for internal refactoring)
  • Add "### Patch Changes" section to the 0.2.191 entry in packages/wagmi-adapter/CHANGELOG.md documenting what changed
🤖 Prompt for AI Agents
In packages/wagmi-adapter/CHANGELOG.md around lines 3–4, the 0.2.191 entry is
missing a "### Patch Changes" section and there is no changeset file recording
the internal refactor; create a new changeset file under .changeset/ describing
a patch bump for packages/wagmi-adapter that summarizes the chain storage
refactoring, updated imports and necessary type casting, and then update
packages/wagmi-adapter/CHANGELOG.md by adding a "### Patch Changes" subsection
under the 0.2.191 header that briefly documents those exact changes (chain
storage refactor, import adjustments, type casts) and references the created
changeset.

@codecov
Copy link

codecov bot commented Nov 24, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 54.82%. Comparing base (52aba0f) to head (39fa990).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8452   +/-   ##
=======================================
  Coverage   54.82%   54.82%           
=======================================
  Files         919      919           
  Lines       60875    60875           
  Branches     4141     4142    +1     
=======================================
  Hits        33374    33374           
  Misses      27400    27400           
  Partials      101      101           
Flag Coverage Δ
packages 54.82% <ø> (ø)
🚀 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.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 24, 2025

size-limit report 📦

Path Size
@thirdweb-dev/nexus (esm) 104.88 KB (0%)
@thirdweb-dev/nexus (cjs) 316.6 KB (0%)

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.

2 participants