creating-changesets

Automate Changesets semantic versioning workflows in Node.js monorepos with Git and PNPM.

29|5|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/saleor/configurator --skill creating-changesets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-changesets
Source: https://github.com/saleor/configurator/tree/main/.claude/skills/creating-changesets
Command: npx skills add https://github.com/saleor/configurator --skill creating-changesets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the creation of changesets for semantic versioning and generates well-documented release notes, ensuring consistent version bumps and changelog entries.

Core Features & Use Cases

  • Changeset generation: Create .changeset entries describing affected packages and bump type.
  • Decision guidance: Correctly choose patch, minor, or major based on changes.
  • Release workflow: Integrates with PRs, changelogs, and version PRs to streamline releases.

Quick Start

Run pnpm changeset to create a new changeset, review the generated entry in .changeset/, then commit and push for release automation.

Frequently Asked Questions about creating-changesets

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

FAQPage Schema
How do I automate semantic versioning and release notes in a monorepo?

Semantic versioning automates version bumps based on change type. Use Changesets with pnpm in Node.js monorepos to create .changeset entries describing affected packages and bump type (patch/minor/major), then generate release notes automatically during the release workflow.

What's the difference between patch, minor, and major version bumps?

Patch fixes bugs without API changes, minor adds backward-compatible features, and major introduces breaking changes. Changesets detect which applies to your changes and applies the correct semantic version bump accordingly.

How do I create a changeset for my changes before opening a PR?

Run pnpm changeset to open an interactive prompt. Select affected packages, choose the bump type, write a brief description, then commit the generated .changeset markdown file. This documents the change for release automation.

Can I use Changesets with pnpm workspaces?

Yes. Changesets integrates directly with pnpm monorepos and workspaces. It detects packages, handles dependencies between them, and coordinates version bumps and changelog entries across your workspace during releases.

What happens to changesets during the release process?

During release, Changesets collects all .changeset entries, applies version bumps to affected packages, generates a consolidated changelog, and creates a version PR. On merge, it publishes updated packages with new versions and release notes.

How do I document breaking changes in a changeset?

When running pnpm changeset, select major as the bump type and describe the breaking change in the changeset file. This ensures it appears prominently in release notes and signals consumers that migration is required.