pyth-sui-js still targets Sui v1 API and cannot be used cleanly with Sui v2 toolchain

Hi team,

We’re trying to upgrade a Sui dApp to the current Mysten stack (@mysten/sui@2.x, @mysten/walrus@1.x, @mysten/dapp-kit@1.x) and found that @pythnetwork/pyth-sui-js still appears tied to Sui v1.

What we observed

• @pythnetwork/pyth-sui-js@3.0.0 declares:
  • @mysten/sui: ^1.3.0
• Its typings import Sui v1 API types:
  • import { SuiClient } from "@mysten/sui/client";
• In @mysten/sui@2.3.1, SuiClient is no longer exported from @mysten/sui/client (client API changed).

Reproduction

1. Create a minimal project with:
   • @mysten/sui@2.3.1
   • @pythnetwork/pyth-sui-js@3.0.0
2. Run pnpm why @mysten/sui

Output shows two Sui versions in the graph:

• top-level @mysten/sui@2.3.1
• nested under pyth: @mysten/sui@1.45.2

This makes it hard to use pyth-sui-js in projects upgraded to Sui v2, and introduces mixed-SDK/type/runtime risk.

Expected behavior

• A pyth-sui-js release compatible with Sui v2 APIs.
• Dependency strategy that avoids pulling a separate Sui v1 copy when app is on Sui v2 (ideally peer dependency / widened compatibility guidance).
• If Sui v2 support is not ready, a clear compatibility matrix and migration timeline would help.

Thanks.

Start by inspecting @pythnetwork/pyth-sui-js@3.0.0 package metadata and the typings that import SuiClient from @mysten/sui/client. Compare those dependencies and imports with @mysten/sui@2.3.1; done means a release supports the Sui v2 API without pulling a separate Sui v1 copy, or documents the compatibility matrix and migration timeline.