Freedom251 › Monorepo Management Tools
Changesets
What Changesets is
Changesets manages package versions and changelogs for monorepos and single-package repositories. Contributors describe release intent in Markdown changeset files, naming affected packages, semantic version bump types, and a summary. Its version command combines those files, applies the highest requested bump for each package, updates dependencies where needed, and writes changelogs. The CLI can then update package versions and changelogs before publishing packages to npm. GitHub teams can use a bot that prompts for changesets on pull requests and an Action to automate versioning and publishing in CI. Supported workspace setups include pnpm, yarn, and npm. Changesets can also manage private applications and non-npm packages, including NuGet packages, Ruby gems, and Docker images, when package.json is present. An optional GitHub changelog package links entries to commits, pull requests, and authors. The tool is self-hosted and free and open source; no paid tiers are listed. The guide requires Node.js ^22.11, ^24, or >=26, with pnpm >=10.0.0, npm >=10.9.0, and yarn >=4.5.2 supported. Changes without a release do not need a changeset.
Who it suits
Changesets suits maintainers coordinating releases across workspaces or single-package repositories, including teams publishing to npm. Its support for private applications and other package types may also fit projects that have package.json.
What it does well
- Supports pnpm, yarn, and npm workspaces
- Automates versioning and publishing through GitHub Action
- Can manage non-npm packages when package.json is present
- No changeset is needed for changes without a release
What to know first
- Requires Node.js ^22.11, ^24, or >=26
- Supported package manager versions have minimum requirements
- Self-hosted
Limits
The free and open-source plan has no paid tiers listed. The documented runtime and package-manager version requirements apply, and non-npm package management requires package.json.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Free and open source | No paid tiers listed | Free |
As changesets.dev lists them, read 4 Oct 2026. The maker's own page has the final word.
Getting started
- Open the Changesets website
- Prepare a self-hosted environment with Node.js ^22.11, ^24, or >=26
- Use pnpm, npm, or yarn at a supported version
- Add Markdown changeset files describing package release intent
- Run the version command to update versions and changelogs
- Use the CLI to publish packages to npm or automate through GitHub
Verdict
Changesets combines contributor-recorded release intent with versioning, changelog, and publishing workflows. Check its Node.js and package manager requirements against your environment.
Questions
How much does Changesets cost?
The listed Free and open source plan costs nothing, and no paid tiers are listed.
Which platforms does it support?
Changesets is self-hosted.
Which package managers are supported?
The listed package managers are pnpm, npm, and yarn, with specified minimum versions.
Can it publish npm packages?
Yes. Its CLI can update package versions and changelogs, then publish packages to npm.
Does it support GitHub workflows?
A GitHub Bot can prompt for changesets on pull requests, and a GitHub Action can automate versioning and publishing in CI.
Are changesets required for every change?
No. Changes that do not require a release do not need a changeset.
Facts from Changesets's own pages
- Automation
- Changesets provides a GitHub Bot to prompt for changesets on pull requests and a GitHub Action to automate versioning and publishing in CI. · changesets.dev, 4 Oct 2026
- Change workflow
- Contributors record release intent in Markdown changeset files with package names, semantic version bump types, and a summary. · changesets.dev, 4 Oct 2026
- GitHub changelogs
- The optional @changesets/changelog-github package links changelog entries to GitHub commits, pull requests, and authors. · changesets.dev, 4 Oct 2026
- Monorepo support
- The site lists pnpm, yarn, and npm workspaces as supported. · changesets.dev, 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. · changesets.dev, 4 Oct 2026
- Not every change needs one
- The FAQ says changes that do not require a release do not need a changeset. · changesets.dev, 4 Oct 2026
- Publishing
- The CLI can update package versions and changelogs, then publish packages to npm. · changesets.dev, 4 Oct 2026
- Publishing security
- The publishing guide advises protecting access tokens and recommends trusted publishing for CI where possible. · changesets.dev, 4 Oct 2026
- Purpose
- Changesets manages package versions and changelog generation for monorepos and single-package repositories. · changesets.dev, 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. · changesets.dev, 4 Oct 2026
- Security guidance
- The automation guide warns against executing untrusted fork code in pull_request_target workflows and recommends narrowly scoped permissions. · changesets.dev, 4 Oct 2026
- Support and funding
- The site describes Changesets as free and open source and links to GitHub sponsorship. · changesets.dev, 4 Oct 2026
- Versioning
- The version command combines changesets, applies the highest specified bump for each package, updates dependencies where needed, and writes changelogs. · changesets.dev, 4 Oct 2026
Where Changesets stands on Freedom251
- Monorepo Management Tools#19 of 33