publish

Category: Development & Coding | Uploader: aave | Downloads: 0 | Version: v1.0（Latest）

Use when manually publishing SDK packages to npm registry, after all changes are merged to main

Changelog: Source: GitHub https://github.com/aave/aave-v4-sdk

Directory Structure

Current level: .claude/skills/publish/

📄 SKILL.md 2.4 KB

SKILL.md

---
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

| Condition | Action |
|-----------|--------|
| Not on main branch | `git checkout main && git pull` first |
| Uncommitted changes | Stash or commit first |
| Tests failing | Fix tests before publishing |
| `pnpm changeset:status` shows no changesets | Nothing to publish - inform user |
| `pnpm whoami` fails | User must run `pnpm login` |
| Major bump in pre-release mode | Confirm 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

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

publish

Directory Structure

SKILL.md

Report

Notice