release-module

Automate Lerna-managed monorepo package releases with versioning and npm publishing.

47|14|Updated Jan 8, 2020
One-click install
npx skills add https://github.com/makeup/makeup-js --skill release-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-module
Source: https://github.com/makeup/makeup-js/tree/main/.claude/skills/release-module
Command: npx skills add https://github.com/makeup/makeup-js --skill release-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually releasing packages in a Lerna-managed monorepo is tedious and error-prone, requiring manual change tracking, version bumping, test validation, and coordinated publishing across multiple interdependent packages. This Skill automates the entire release workflow to eliminate manual overhead and reduce the risk of human error.

Core Features & Use Cases

  • Automatic Change Detection: Leverages Lerna to identify all packages with changes since the last release, including downstream dependents, ensuring no packages are accidentally omitted from releases.
  • Guided End-to-End Workflow: Handles prerequisite validation, full test suite execution, automated version bumping, local commit and tag creation, and step-by-step npm publishing guidance with built-in error handling for common issues like uncommitted changes or 2FA prompts.
  • Use Case: For teams maintaining the makeup-js accessible UI component monorepo, this Skill cuts release time from hours of manual work to a few guided steps, ensuring consistent and reliable package publishes to npm and GitHub.

Quick Start

Use the release-module skill to publish all changed packages in the makeup-js monorepo with a patch version bump.

Frequently Asked Questions about release-module

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

FAQPage Schema
How do I automate package versioning and npm publishing in a Lerna monorepo?

Automating Lerna monorepo releases involves detecting changed packages, bumping versions, and publishing to npm. This workflow handles prerequisite validation, automated version bumping, and step-by-step npm publishing guidance to eliminate manual overhead.

What is the best way to handle coordinated releases for independent packages in a JavaScript monorepo?

Coordinated JavaScript monorepo releases require tracking downstream dependents to ensure no packages are omitted. This automated process identifies all changed packages since the last release and applies independent or coupled version bumps.

How do I resolve npm 2FA prompts when publishing multiple monorepo packages?

Resolving npm 2FA prompts during monorepo package publishing requires guided step-by-step execution. The workflow includes built-in error handling for 2FA prompts and common publishing issues to ensure reliable releases.

Does Lerna automatically update versions for downstream dependent packages in a monorepo?

Lerna automatically identifies packages with changes and their downstream dependents. This ensures all affected packages in the monorepo receive appropriate version bumps and are included in the coordinated release.

What are the limitations of automating Lerna monorepo releases with uncommitted changes?

Automated Lerna releases require a clean working state. The workflow includes prerequisite validation that halts the release process if uncommitted changes are detected, preventing inconsistent package states.

How do I validate and test monorepo packages before an automated npm publish?

Validating monorepo packages before npm publishing requires running the full test suite. This workflow executes prerequisite validation and tests prior to automated version bumping and git tag creation.