skills.rest
ueberBrot
ueberBrotCOMMUNITY
Explore all skills by this author →
GitHub

changeset-management

Manage versions and changelogs in multi-package repositories with Changesets.

3|1|Updated Dec 17, 2025
Search Tags:#changelog#versioning#CI/CD#monorepo#bun#release-management#changesets
One-click install
npx skills add https://github.com/ueberBrot/monque --skill changeset-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changeset-management
Source: https://github.com/ueberBrot/monque/tree/main/.github/skills/changeset-management
Command: npx skills add https://github.com/ueberBrot/monque --skill changeset-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to manage versions and changelogs using Changesets, ensuring reliable and auditable releases.

Core Features & Use Cases

  • Create changesets to bump package versions in a multi-package repository.
  • Generate empty changesets to satisfy CI when no user-facing changes occurred.
  • Follow a repeatable release workflow with build and publish steps.

Quick Start

Run bun changeset to create a new changeset, select the changed packages, and choose the bump type. Then run bun run build followed by bun run release to publish.

Frequently Asked Questions about changeset-management

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

FAQPage Schema
How do I manage versions and changelogs in a Bun monorepo?▼

To manage versions and changelogs in a Bun monorepo, you create changesets to declare updates, then execute build and release scripts to bump package versions and publish them automatically.

How do I create a changeset to bump package versions in a multi-package repository?▼

You create a changeset by running bun changeset, selecting the modified packages, and choosing the bump type to ensure proper versioning and changelog documentation for the release.

Why does CI fail on empty changesets in a monorepo and how to fix it?▼

CI fails when it expects changesets but none exist for a commit. You fix this by generating an empty changeset to satisfy CI requirements when no user-facing changes occurred.

What is the standard release workflow for publishing multi-package repositories with Bun?▼

The standard release workflow involves running bun changeset to record updates, followed by bun run build to compile, and finally bun run release to publish the packages and update changelogs.

When should I generate an empty changeset during the release process?▼

You should generate an empty changeset during the release process when no user-facing changes occurred, ensuring your CI checks pass and maintaining a repeatable, auditable release workflow.

Related Skills

Explore More Software Engineering Skills→
pohlai88pohlai88

pnpm-workspace

Define pnpm-workspace.yaml and link local packages with the workspace protocol.

Community
Intermediate
louisbrulenaudetlouisbrulenaudet
18

tanstack-config

Standardize JavaScript and TypeScript package configuration with Vite, ESLint, and publishing automation.

Community
Advanced
MichealWayneMichealWayne
207

build-packages

Build fe-tools monorepo packages and validate TypeScript compilation.

Community
Intermediate
voidrotvoidrot

changelog-automation

Generate changelogs and release notes from commit history and tags.

Community
Advanced