versioning

Generate per-PR changesets and changelogs for multi-package repositories.

9|2|Updated Apr 13, 2024

Search Tags:#automation #changelog #versioning #monorepo #semver #changesets

Ready to run

npx skills add https://github.com/JacobLey/leyman --skill versioning-jacobley

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/JacobLey/leyman/tree/main/.claude/skills/versioning
Command: npx skills add https://github.com/JacobLey/leyman --skill versioning-jacobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Versioning and changelog generation for multi-package repos using Changesets, ensuring consistent releases and traceable history.

Core Features & Use Cases

Generate per-PR changeset files to record version bumps
Guide semver decisions (patch, minor, major) and automate changelog updates
Works in monorepos to coordinate package versioning and publishing

Quick Start

After making changes, run changeset to create a changeset file and commit it with your PR.

Frequently Asked Questions about versioning

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

FAQPage Schema

How do I automate changelog generation and versioning in a monorepo?▼

Automate changelog generation and versioning in a monorepo by generating per-PR changeset files that record semantic version bumps. This coordinates package versioning and publishing while ensuring consistent releases and traceable history across multi-package repositories.

How do changesets work for managing semantic versioning across multiple packages?▼

Changesets work by generating a markdown file per pull request that records the patch, minor, or major version bump. These files are committed alongside code changes to automate changelog updates and coordinate semver decisions across all affected packages.

Do I need a config.json file to start using changesets for package publishing?▼

Yes, you need changeset tooling installed and a configured .changeset/config.json file to use changesets for package publishing. After making code changes, run the changeset command to create a changeset file and commit it with your PR.

When should I use changesets for semver versioning instead of manual package updates?▼

Use changesets for semver versioning when managing multi-package repositories that publish to a registry. It replaces manual package updates by guiding per-PR version bump decisions and automating changelog generation to maintain a traceable release history.

What is the best way to coordinate package versioning and publishing in a multi-package repository?▼

The best way to coordinate package versioning and publishing in a multi-package repository is using changesets. This approach records per-PR version bumps, automates changelog updates, and guides semantic versioning decisions to ensure consistent and coordinated releases.