release-ts-sdk

name	release-ts-sdk
description	Use when cutting a release of @aptos-labs/ts-sdk or @aptos-labs/confidential-asset. Phase 1 bumps the version, stamps the changelog, and opens the release PR. Phase 2 (after the PR merges to main) cuts the tag and GitHub Release that triggers the NPM publish workflow.

Releasing the Aptos TypeScript SDK

Two packages release independently:

• @aptos-labs/ts-sdk (repo root) — tag prefix ts-sdk-v
• @aptos-labs/confidential-asset (confidential-asset/) — tag prefix confidential-asset-v

All mechanical work is done by scripts/prepareRelease.mjs. Publishing to NPM is done by .github/workflows/publish.yaml when a GitHub Release is published — never publish by hand.

Preconditions

• Working tree clean, on an up-to-date main.
• The target package's # Unreleased changelog section already lists the changes being released. If it is empty, stop and ask the maintainer to fill it in first (the script will refuse otherwise).

Phase 1 — prepare the release PR

1. Ask which package (ts-sdk or confidential-asset) unless it is obvious from context.
2. Ask the bump type: major, minor, or patch. For a major bump, remind the maintainer to write an upgrade guide at upgrade-guides/UPGRADE_GUIDE_X.Y.Z.md and reference it in the changelog.
3. Determine the new version without mutating anything yet: read version from the package's package.json (. for ts-sdk, confidential-asset/ for confidential-asset) and apply the bump.