skills.rest
motormetrics
motormetricsOFFICIAL
Explore all skills by this author →
Website𝕏@motormetricsGitHub

release-management

Automate versioning and changelog generation across a monorepo with semantic-release.

21|2|Updated Nov 5, 2023
Search Tags:#git#changelog#versioning#monorepo#release-management#ci-cd#semantic-release
One-click install
npx skills add https://github.com/motormetrics/motormetrics --skill release-management-motormetrics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-management
Source: https://github.com/motormetrics/motormetrics/tree/main/.claude/skills/release-management
Command: npx skills add https://github.com/motormetrics/motormetrics --skill release-management-motormetrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes software releases across a monorepo using semantic-release, ensuring consistent version bumps and up-to-date changelogs.

Core Features & Use Cases

  • Automates version bumps across all packages in a monorepo based on conventional commits.
  • Updates CHANGELOG.md automatically and creates GitHub releases with notes.
  • Validates branches and CI readiness, with support for emergency manual releases when needed.

Quick Start

Set up semantic-release in the repository and run the release workflow to publish a new version.

Frequently Asked Questions about release-management

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

FAQPage Schema
How do I automate semantic-release versioning and changelogs in a monorepo?▼

To automate semantic-release versioning in a monorepo, you need a .releaserc.json configuration and conventional commit messages. The workflow triggers on main branch pushes, automatically standardizing version bumps and generating changelogs across all packages.

What is needed to trigger automatic version bumps across multi-package repositories?▼

Triggering automatic version bumps across multi-package repositories requires proper conventional-commits messages and pushes to the main branch. This setup ensures semantic-release accurately evaluates commit history to produce tags, release notes, and GitHub releases.

Does semantic-release work with conventional commits for GitHub release generation?▼

Yes, semantic-release works directly with conventional commits to drive GitHub release generation. It validates branch readiness, automatically updates your CHANGELOG.md, and creates GitHub releases with notes based on the commit message history.

Can I do a manual emergency release if the automated CI workflow fails?▼

Yes, you can perform an emergency manual release when needed. While the standard process validates branches and CI readiness to automate releases on main branch pushes, the workflow supports manual interventions for urgent deployment scenarios.

Why are my monorepo package versions not updating automatically?▼

Monorepo package versions fail to update automatically if conventional-commits messages are improperly formatted or the .releaserc.json configuration is missing. Accurate semantic-release processing strictly relies on these commit conventions to calculate and apply version bumps.

Related Skills

Explore More Software Engineering Skills→
Fantasia1999Fantasia1999

changelog-generator

Generate changelog entries from Conventional Commits in Markdown or JSON formats.

Community
Advanced
sync-dev-orgsync-dev-org

sdd-publish-setup

Generate GitHub Actions workflows for publishing Python, TypeScript, and Rust packages.

Official
Advanced
ricardorochericardoroche
2

git-workflow-standards

Enforce conventional commits, branch naming, PR templates, and semantic versioning.

Community
Intermediate
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced