release

Publish npm packages, update versions, and tag releases across a monorepo.

39|11|Updated Dec 10, 2019
One-click install
npx skills add https://github.com/alps-asd/app-state-diagram --skill release-alps-asd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/alps-asd/app-state-diagram/tree/main/docs/skills/release
Command: npx skills add https://github.com/alps-asd/app-state-diagram --skill release-alps-asd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the multi-package release workflow by automating npm package publishes, version bumps, and git tagging across a monorepo.

Core Features & Use Cases

  • Automated version bumps and package publishing across packages to keep all packages synchronized.
  • Publish in dependency order (core packages first) and propagate updates to workspace references.
  • Create and push git tags for new releases, with optional alpha/stable tagging and Homebrew formula updates when applicable.

Quick Start

Run the release skill to publish all packages, update workspace references, and push git tags for the new version.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm package publishing and version bumps in a monorepo?

Automating npm package publishing and version bumps in a monorepo is handled by propagating updates to workspace references and publishing packages in a defined dependency order. This ensures all interdependent packages stay synchronized without manual intervention.

Can I publish monorepo packages in dependency order so core packages go first?

Yes, you can publish monorepo packages in dependency order, ensuring core packages are published first. The release workflow automatically propagates these core version updates to dependent workspace references before publishing them.

How do I create and push git tags for new releases across multiple packages?

Creating and pushing git tags for new releases across multiple packages is automated during the release workflow. The process optionally supports alpha and stable tagging strategies to differentiate pre-release and production versions.

Does the monorepo release workflow run builds and tests before publishing npm packages?

Yes, the monorepo release workflow runs builds and tests before publishing npm packages. This ensures that only successfully built and validated packages are published to the registry and tagged in git.

Can I update Homebrew formulas when publishing new npm package versions?

Yes, you can update Homebrew formulas when publishing new npm package versions. The release workflow includes optional formula updates alongside standard version bumps and git tag creation for applicable packages.

What is the best way to keep multiple interdependent packages synchronized during a release?

Keeping multiple interdependent packages synchronized during a release is best handled by automating version bumps and workspace reference updates. This guarantees consistent versions across the monorepo by publishing in dependency order.