Bump the Sui pin to $ARGUMENTS (a mainnet-vX.Y.Z or testnet-vX.Y.Z
tag). Full checklist: dev-docs/conventions/sui-version-bump.md. Work
on a dedicated branch.
- Read the CURRENT tag (single distinct value) from root
Cargo.toml. - Replace it in every root
Cargo.tomlpin (~90 occurrences, one sed), thencargo update. - Excluded workspaces:
(cd sdk/ika-wasm && cargo update)(and any other excluded package with its own lock). - Update the sui-binary download URLs (tag appears twice per URL) in
.github/workflows/ts-integration-tests.yamland.github/workflows/ts-ci.yaml, and the pinned-version gotcha inCLAUDE.md. - msim compatibility: compare the new Sui workspace's tokio version
against the
msimrev's; if they differ, the[patch.crates-io.tokio]silently no-ops — find an msim rev shipping the matching tokio. - Verify:
./scripts/check-sui-version-consistency.sh(CI enforces it), thencargo build --release, then dispatch the integration suite (/dispatch-suites) — crypto and consensus layers are the usual cross-version breakage points. Watch for#[cfg(msim)]rot (unresolved importunder--cfg msim). - In the PR description, tell developers to update their local
suibinary — a mismatched localnet binary completes DKG but silently stalls reconfiguration (dev-docs/playbooks/localnet.md).