@changesets/cli
- 3.0.3 is the latest, published 14 September 2026.
- No known security advisory.
- 3.x: 4 releases since 11 August 2026, 4 in the last 90 days.
Releases in the last 90 days
Feed of releases and advisoriesEvery stable release, newest first. Notes are quoted as the maintainers published them.
3.0.3
14 September 2026Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.
Patch Changes
Fixed semver ranges (such as
>=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.
Updated dependencies:
@changesets/apply-release-plan@8.1.1
@changesets/config@4.0.1
3.0.2
4 September 2026Add review message on pre exit
Patch Changes
Add review message on pre exit
Updated dependencies:
@changesets/apply-release-plan@8.1.0
@changesets/git@4.0.1
@changesets/read@1.0.1
3.0.1
19 August 2026Update links in default generated .changeset/README.md file
Patch Changes
Update links in default generated
.changeset/README.mdfileUpdated dependencies:
@changesets/write@1.0.1
3.0.0
11 August 2026Renamed the changeset tag command to changeset git-tag.
Major Changes
Renamed the
changeset tagcommand tochangeset git-tag.Set supported package manager versions in
"engines"field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.changeset versionnow exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using
--snapshotmode.Bumped supported Node versions to
^22.11 || ^24 || >=26The
prettieroption in.changeset/config.jsonhas been removed in favor offormat.formatsupports"auto","prettier","oxfmt","deno", and"dprint", andfalsedisables formatting. If you previously usedprettier: false, migrate toformat: falseor remove the option to use automatic formatter detection.Move versioned prerelease changesets to
.changeset/pre/folder instead of accumulating in the root and tracking the versioned changeset ids in the.changeset/pre.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset status.This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in
.changeset/pre/can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids inpre.jsonif certain changesets are deleted.Removed Yarn Classic support
Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign
latesttag. npm registry itself does that and such packages will continue to be released withlatesttag (and not with the configured prerelease tag).Removed warning messages about using v1 configs. They will now be silently ignored.
Update
@manypkg/get-packageswhich drops support for detecting packages in Bolt monorepos and adds support for npm monoreposRemove support for the
--sinceMasterflag forchangeset status. Use--since=masteror--since=maininstead.Remove the
pre.jsoninitialVersionsproperty and handling as it's unused internallyCommitFunctionscan now be both sync and async, and thedefaultCommitFunctionsare now sync.From now on this package is going to be published as ES module.
Remove support for the deprecated
___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshotsconfig. Thesnapshot.useCalculatedVersionconfig should be used instead.Private packages are no longer versioned by default. Set
privatePackagestotrueto opt into versioning and tagging them, or setprivatePackages.versiontotrueto version them without tagging.Migrated from
enquirer+@inquirer/launch-editorto@clack/prompts+launch-editor.This means the CLI flows will have minor changes, but they are largely the same.
This change also fixes various issues related to
enquirerlike cancelling prompts crashing the CLI.Peer dependencies now bump packages that depend on them by
patchinstead ofmajor.This means a peer dependency update is no longer assumed (forced) to be a breaking change.
If the dependent package is not compatible with the peer's new release you should manually add a
majorchangeset describing why and how to migrate.
Minor Changes
Added new
--major,--minor,--patchflags to theaddcommand.Allow comma-separated values in array-valued CLI flags: the
--major,--minor, and `--pat
Major versions
- 3.xsince 11 August 2026 · latest 3.0.3 · 4 releases
- 2.xsince 13 September 2019 · latest 2.31.1 · 94 releases
- 1.xsince 6 May 2019 · latest 1.3.3 · 12 releases
Quality and security signals
What npm and deps.dev say about the latest release. Signals, not a verdict.
Reading npm and deps.dev…
Registry facts last checked 15 October 2026. Releases and advisories last read 14 October 2026.
Know when your own dependencies move
Inlinr tracks your coding time automatically. Switch dependency tracking on for a project and it reads that repository's manifest to show what is behind and what has been deprecated — off by default, one project at a time.