# Bump Chain Sdk > Bump an Aptos/Sui/Iota SDK version in this monorepo, regenerate builtin and test types, run tests, and prepare a conventional commit. Use when the user asks to upgrade @aptos-labs/ts-sdk, @mysten/sui, @iota/iota-sdk, or any chain SDK version. Use when this capability is needed. - Skill: `tomevault-io/bump-chain-sdk` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/bump-chain-sdk` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/bump-chain-sdk/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/bump-chain-sdk --- # Bump Chain SDK Upgrade an Aptos / Sui / Iota SDK version inside this typemove monorepo and propagate the changes through codegen + tests + commit. ## When to use User says something like: - "Bump Iota SDK to 1.10.0" - "Upgrade Sui SDK to the latest" - "Update @aptos-labs/ts-sdk to 6.1.0" ## Inputs to confirm Before doing anything, confirm with the user: - **Chain**: `aptos`, `sui`, or `iota` - **Target version**: e.g. `1.10.0`, or `latest` if they want you to pick ## Steps 1. **Locate the target package.json** - `packages/aptos/package.json` → `@aptos-labs/ts-sdk` - `packages/sui/package.json` → `@mysten/sui` - `packages/iota/package.json` → `@iota/iota-sdk` - Some upgrades also touch the root `package.json` (see commit `472da443` for the Iota 1.10.0 precedent — root `package.json` and `pnpm-lock.yaml` were updated alongside the chain package). 2. **Update the version** in package.json and run `pnpm install` from the repo root to refresh `pnpm-lock.yaml`. 3. **Regenerate builtin types** for the affected chain. Run from the chain package directory: ```bash cd packages/ && pnpm gen ``` This regenerates `src/builtin/0x1.ts`, `0x2.ts`, `0x3.ts` (Sui/Iota) or `0x1.ts`, `0x3.ts`, `0x4.ts` (Aptos). 4. **Regenerate test types**: ```bash cd packages/ && pnpm gen:test ``` 5. **Build the package** to surface any breakage from SDK API changes: ```bash pnpm --filter @typemove/ build ``` If TypeScript errors appear, they are almost always SDK breaking changes — fix them in `move-coder.ts`, `to-internal.ts`, `chain-adapter.ts`, or the codegen output. Don't hand-edit `src/builtin/` files — fix the codegen source instead. 6. **Run tests for the chain**: ```bash pnpm --filter @typemove/ test ``` 7. **Check sibling chains for shared breakage**. SDK upgrades sometimes change shared @typemove/move interfaces. If you touched anything outside `packages//`, run `pnpm test:all` and `pnpm build:all`. 8. **Stage and commit** using the canonical message format from history: ``` chore: upgrade SDK to ``` Examples from `git log`: `chore: upgrade Iota SDK to 1.10.0`, `chore: upgrade Sui SDK to 2.4.0`. Note: these specific upgrade commits use a bare `chore:` prefix without a scope, even though `CLAUDE.md` recommends `chore(deps):` generally. Follow the existing pattern for chain-SDK bumps. 9. **Create the PR** per CLAUDE.md: this repo is PR-only, never push to main. Use `git dev /bump--` (custom shortcut from `.github/.gitconfig`) or `git checkout -b dev//bump--`, then `gh pr create`. ## Things to watch for - **GitHub Actions workflows** sometimes need a matching version bump (e.g. `472da443` touched all four `.github/workflows/*.yaml` files). Grep `.github/workflows/` for the old version string before committing. - **iota `sync-from-sui` script**: Iota's codegen historically mirrors Sui's. If you bump Sui you may also want to run `pnpm --filter @typemove/iota sync-from-sui` and re-test Iota. - **Don't manually edit `packages/*/src/builtin/0x*.ts`** — they are codegen outputs and a PreToolUse hook will block edits. --- > Source: [sentioxyz/typemove](https://github.com/sentioxyz/typemove) — distributed by [TomeVault](https://tomevault.io).