Changesets

What it does

Automation

Changesets provides a GitHub Bot to prompt for changesets on pull requests and a GitHub Action to automate versioning and publishing in CI.checked 4 Oct 2026

Change workflow

Contributors record release intent in Markdown changeset files with package names, semantic version bump types, and a summary.checked 4 Oct 2026

GitHub changelogs

The optional @changesets/changelog-github package links changelog entries to GitHub commits, pull requests, and authors.checked 4 Oct 2026

Monorepo support

The site lists pnpm, yarn, and npm workspaces as supported.checked 4 Oct 2026

Non-npm projects

Changesets can manage private applications and non-npm packages such as NuGet packages, Ruby gems, and Docker images when package.json is present.checked 4 Oct 2026

Not every change needs one

The FAQ says changes that do not require a release do not need a changeset.checked 4 Oct 2026

Publishing

The CLI can update package versions and changelogs, then publish packages to npm.checked 4 Oct 2026

Publishing security

The publishing guide advises protecting access tokens and recommends trusted publishing for CI where possible.checked 4 Oct 2026

Purpose

Changesets manages package versions and changelog generation for monorepos and single-package repositories.checked 4 Oct 2026

Runtime requirements

The guide requires Node.js ^22.11, ^24, or >=26 and lists pnpm >=10.0.0, npm >=10.9.0, and yarn >=4.5.2 as supported package managers.checked 4 Oct 2026

Security guidance

The automation guide warns against executing untrusted fork code in pull_request_target workflows and recommends narrowly scoped permissions.checked 4 Oct 2026

Support and funding

The site describes Changesets as free and open source and links to GitHub sponsorship.checked 4 Oct 2026

Versioning

The version command combines changesets, applies the highest specified bump for each package, updates dependencies where needed, and writes changelogs.checked 4 Oct 2026