OSS Tanbou
View on GitHubProject website

record SemVer bump intent and changelog notes with each change, then coordinate version updates and package publishing across monorepos

OSS scale score 257.8OSS health 89Update pace 18 commits/30d
About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
12,466
Primary language
TypeScript
License
MIT
Repository last updated
Sep 27, 2026
On this page

Overview

Changesets is a CLI and workflow for package versioning and changelog management. Contributors record the affected packages, SemVer bump types, and release notes in Markdown changeset files, then release tooling consumes those files to update versions and changelogs. It is designed especially for monorepos and their internal dependency relationships.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Record package and SemVer bump intent alongside each change

A changeset is a Markdown file whose YAML frontmatter lists packages and patch, minor, or major bump types while the body carries the changelog summary.

Sources: [2]

Coordinate related package versions in monorepos

Changesets focuses on monorepos and can account for dependencies between packages when assembling release plans, while the workflow also works for single-package repositories.

Sources: [1][2]

Run versioning, changelog updates, and publishing through one CLI

changeset version consumes accumulated changesets and updates package versions and changelogs, while changeset publish publishes updated packages and creates Git tags.

Sources: [3]

Best fit

Fits monorepos where packages release independently

It is useful for library sets, design systems, and other repositories where packages have different release timing and SemVer changes and contributor intent should be preserved for a later release step.

Sources: [1][2]

Before adoption

Do not require changesets for changes that do not produce releases

The official guide says changes that do not need a release do not require a changeset and recommends against making the absence of a changeset a universal contribution blocker.

Sources: [2]

Protect publishing credentials and push generated tags

Publishing requires registry permissions. The guide warns against leaking access tokens, recommends trusted publishing where practical, and notes that generated Git tags need to be pushed to the remote.

Sources: [3]

Meet the CLI 3.0.3 Node and package-manager requirements

Version 3.0.3 requires Node ^22.11 || ^24 || >=26 and supports npm 10.9+, pnpm 10+, and Yarn 4.5.2+. Align CI runtimes before adopting the v3 CLI.

Sources: [2][4][5]

Official sources

  1. [1]Changesets CLI 3.0.3 README(2026-10-03)
  2. [2]Changesets 3.0.3 getting started(2026-10-03)
  3. [3]Changesets 3.0.3 versioning and publishing(2026-10-03)
  4. [4]@changesets/cli 3.0.3 package metadata(2026-10-03)
  5. [5]@changesets/cli 3.0.3 release(2026-10-03)
  6. [6]Changesets MIT license(2026-10-03)
Supplemental curator note

Changesets captures release intent while the contributor still has context about the change. Avoid making a changeset mandatory for every commit; define how documentation, tests, and other non-release changes should be handled by the team.

Try it in 3 steps

  1. 1

    Add Changesets CLI 3.0.3 as a development dependency

    Pin the CLI in an existing package project using Node ^22.11 || ^24 || >=26 and npm 10.9 or newer.

    npm install --save-dev @changesets/cli@3.0.3
  2. 2

    Initialize the .changeset configuration

    Create the .changeset directory and configuration that drives version and changelog management.

    npx changeset init
  3. 3

    Record the change and its SemVer bump

    Interactively select packages, patch/minor/major bump types, and a changelog summary, then commit the generated Markdown file with the change.

    npx changeset
Check the official README

Growth

Growth trends · Last 30 days

12,466 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
18
Open PRs
76

Development activity is still being collected.

Built with

Categories and tags

Categories

Tags

GitHub data

GitHub dataView detailed GitHub data
View on GitHub
Stars
12,466
Forks
840
Watchers
45
Open issues
194
Contributors
198
Owner type
Organization
Primary language
TypeScript
License
MIT
Repository last updated
Sep 27, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?