publish

Publish Aave SDK packages to npm with changesets and git tags.

22|19|Updated Sep 1, 2025
One-click install
npx skills add https://github.com/aave/aave-v4-sdk --skill publish-aave
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/aave/aave-v4-sdk/tree/main/.claude/skills/publish
Command: npx skills add https://github.com/aave/aave-v4-sdk --skill publish-aave

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates publishing of Aave SDK packages to npm after changes are merged to main, reducing manual steps and preventing human error.

Core Features & Use Cases

  • Automates version bumps via changesets and publishes all affected packages to npm.
  • Handles authentication, OTP prompts, and git tagging to ensure traceability.
  • Integrates into CI/CD workflows to streamline release cycles for SDKs.

Quick Start

Run the publish workflow on the main branch to publish all updated packages to npm.

Frequently Asked Questions about publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate npm package publishing with changesets after merging to the main branch?

You can automate npm package publishing by running a workflow that uses changesets to handle version bumps and publish all affected packages automatically after changes merge to main.

What do I need to configure to publish npm packages with OTP authentication and git tags?

To publish npm packages with OTP and git tags, you need pnpm, changesets, npm authentication configured with OTP, and git access to perform the publish and push operations.

Does changesets support monorepo workflows for publishing multiple SDK packages to npm?

Yes, changesets supports monorepo workflows by detecting affected packages, applying version bumps, and publishing all updated SDK packages to npm while creating git tags for traceability.

What is the best way to handle version bumps and release management for Aave SDK packages?

The best way to handle version bumps for Aave SDK packages is using changesets integrated into a CI/CD workflow, which automates versioning, npm publishing, and git tag creation on the main branch.

Why does npm publish fail with OTP prompts in automated CI/CD release workflows?

npm publish fails with OTP prompts in CI/CD when authentication is not properly configured; this workflow handles OTP prompts and npm authentication to ensure automated releases succeed.

Can I use pnpm with changesets to publish packages without manual version management?

Yes, you can use pnpm with changesets to publish packages without manual version management, as the workflow automates version bumps and publishes all affected packages directly to npm.