AgentSkillsCN

publish

在所有变更合并至主分支后，手动将SDK软件包发布至npm注册表时，此功能尤为实用。

SKILL.md
--- frontmatter
name: publish
description: Use when manually publishing SDK packages to npm registry, after all changes are merged to main

Publish SDK Packages

Publishes @aave packages to npm using changesets.

Checklist

You MUST use TodoWrite to create a todo for EACH step below. Mark each complete only after verification.

Pre-flight

  • • Verify on main branch and up-to-date: git checkout main && git pull
  • • Verify working directory is clean: git status shows no uncommitted changes
  • • Run nvm use to ensure correct Node.js version
  • • Run corepack enable to ensure correct pnpm version
  • • Run pnpm install to update dependencies
  • • Run pnpm build to build all packages

Version Bump

  • • Run pnpm changeset:status to check for pending changesets (if none exist, nothing to publish - STOP)
  • • Run pnpm changeset:version to bump versions
  • • Review output: if in pre-release mode and "major" bumps appear, ask user to confirm
  • • Stage and commit: git add . && git commit -m "chore: bumps up versions"

Publish

  • • Verify npm authentication: run pnpm whoami
    • •If it fails: ask user to run pnpm login then re-verify
  • • Ask user for npm OTP code (from authenticator app)
  • • Run NPM_CONFIG_OTP=<otp> pnpm changeset:publish with the provided OTP
    • •If OTP expires mid-publish: ask for new OTP and retry failed packages manually
    • •If publish fails partially: check npm for which packages published, may need manual recovery
  • • Run git push --follow-tags

Stop Conditions

ConditionAction
Not on main branchgit checkout main && git pull first
Uncommitted changesStash or commit first
Tests failingFix tests before publishing
pnpm changeset:status shows no changesetsNothing to publish - inform user
pnpm whoami failsUser must run pnpm login
Major bump in pre-release modeConfirm with user - may be unintentional

Pre-release Mode

When .changeset/pre.json exists:

  • •Packages publish with -next.N suffix (e.g., 4.1.0-next.16)
  • •Major version bumps should be rare - verify intentional
  • •The tag field in pre.json shows the npm dist-tag (next)

Common Mistakes

  1. •Skipping nvm use - Wrong Node version causes build failures
  2. •Forgetting --follow-tags - Git tags not pushed, npm versions unlinked
  3. •Not checking pre-release mode - Accidental major version bumps