Changesets

Patch Changes

• #2239 fdfdc93 Thanks @bluwy! - Update links in default generated .changeset/README.md file
• Updated dependencies [d0386b6]:
  • @changesets/write@1.0.1

Major Changes

• #2128 7113c01 Thanks @Andarist! - Renamed the changeset tag command to changeset git-tag.

• #2074 3599e47 Thanks @bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

• #1860 92b1c1b Thanks @mixelburg! - changeset version now 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 --snapshot mode.

• #1482 df424a4 Thanks @Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

• #1994 062530b Thanks @bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

• #2190 96b65ee Thanks @bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset 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 in pre.json if certain changesets are deleted.

• #2145 f5887ff Thanks @Andarist! - Removed Yarn Classic support

• #2097 8c88f6a Thanks @Andarist! - 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 latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

• #1879 c76b232 Thanks @beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

• #1655 db46911 Thanks @bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

• #1651 e1df862 Thanks @bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

• #2117 813bbf3 Thanks @bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

• #1961 07278a7 Thanks @beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

• #1482 df424a4 Thanks @Andarist! - From now on this package is going to be published as ES module.

• #1652 a0b5326 Thanks @bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

• #2186 3910adf Thanks @Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

• #1879 c76b232 Thanks @beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @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 enquirer like cancelling prompts crashing the CLI.

• #2090 3aae903 Thanks @beeequeue! - Peer dependencies now bump packages that depend on them by patch instead of major.

  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 major changeset describing why and how to migrate.

Minor Changes

• #1121 ce2095d Thanks @Sh031224! - Added new --major, --minor, --patch flags to the add command.

• #2135 fd7724a Thanks @youdie006! - Allow comma-separated values in array-valued CLI flags: the --major, --minor, and --patch flags of the add command, and the --ignore flag of the version command. For example, --minor pkg-a,pkg-b is now equivalent to --minor pkg-a --minor pkg-b. Surrounding whitespace is trimmed and empty entries are ignored.

• #2068 d03ffc1 Thanks @bluwy! - Support {commit-short} placeholder for the snapshot.prereleaseTemplate config, which is a 7 character variant of {commit}

• #2061 c2db1dd Thanks @Andarist! - Added a changeset publish-plan command to inspect which packages would be published or tagged, with optional JSON output.

• #2087 edc30c8 Thanks @trueberryless! - Made the init command interactive. Running changeset init will now guide you through a set of intuitive prompts to configure your changelog generator, commit preferences, publish access, and base branch, rather than silently writing the default configuration file.

• #1969 2c7c043 Thanks @marcalexiei! - Add a named export that mirrors the current default export

  The default export is slated for removal in the next major release, so this ensures a smoother transition path.

• #1879 c76b232 Thanks @beeequeue! - Packages are now listed in alphabetical order when possible.

• #2129 369eb0b Thanks @Andarist! - Commands supporting --output (such as status and publish-plan) can now be invoked with CHANGESETS_OUTPUT=path/to/file environment variable. This has the same effect as calling them with --output=path/to/file

• #2100 90b4ad0 Thanks @Andarist! - Order releases into dependency-aware chunks so packages are grouped in publish order.

• #2136 2f9ca42 Thanks @bluwy! - Remove confirmation prompt when adding a changeset. It will always add a changeset instead, and if the changeset is not desired, the user can edit or delete the file directly.

• #2155 5a8119b Thanks @beeequeue! - Improved changeset publish failure handling. Errors are reported per package, successful publishes are still tagged when another package fails, and authentication retries avoid republishing completed packages.

• #2063 ed77176 Thanks @Andarist! - Added changeset publish --from-pack-dir <dir> to publish packages from a previously created pack output directory.

• #2062 830443c Thanks @Andarist! - Added a changeset pack command that requires --out-dir and writes publishable package tarballs plus an enriched publish-plan.json into that directory, either from the current workspace or from a saved publish plan via --from-plan.

• #1879 c76b232 Thanks @beeequeue! - Choosing a change type now shows a preview of which part of the version it affects.

  Which packages should have a major (X.X.X) bump?

• #2129 369eb0b Thanks @Andarist! - changeset publish and changeset tag can now be invoked with CHANGESETS_OUTPUT=path/to/file environment variable. They produce output in the NDJSON format.

• #2130 18bc470 Thanks @beeequeue! - Allow unmatched glob patterns in the ignore config option.

• #2073 b9cbd80 Thanks @bluwy! - Show if a package is private when selecting packages in changeset add

Patch Changes

• #1476 e0e1748 Thanks @pralkarz! - Replace fs-extra usage with node:fs

• #2060 11bded4 Thanks @Andarist! - Fixed changeset publish to respect ignored packages for both publishing and private package tagging.

• #2041 ce39c72 Thanks @bluwy! - Enable guide line for add command and use box design for dependent patch bump note

• #2064 ffd65fc Thanks @Andarist! - For pnpm projects, Changesets now match pnpm's native registry behavior more closely during unpublished package checks. Both scope-based publishConfig registry overrides and publishConfig.registry are now ignored.

• #2002 6db2c21 Thanks @Andarist! - Lazy-load CLI commands so changeset only loads the code needed for the command being run.

• #2097 8c88f6a Thanks @Andarist! - Route package manager calls through their respective CLIs during publish (npm, pnpm, yarn). Notably, Yarn Berry publishes now let Yarn update workspace protocol ranges as part of the publish process.

• #2132 d35bb77 Thanks @cyphercodes! - Improve publish error handling for npm and pnpm JSON errors. Changesets now skips npm 11 already-published errors that omit code, correctly skips pnpm 11 already-published errors, and retries pnpm 11 ERR_PNPM_OTP_NON_INTERACTIVE publish failures in delegated interactive mode.

• #2160 162419d Thanks @beeequeue! - Added or modified the files property in the manifest. This should not change any behavior.

• #2009 44df27d Thanks @bluwy! - Use cac for CLI arg parsing and handling

• #2113 b8222e6 Thanks @Andarist! - Fixed publish error printing for pnpm 11.

• #2065 0598e83 Thanks @Andarist! - Improved changeset publish auth handling by removing the preflight OTP requirement check and falling back to interactive auth when the package manager reports that authentication is required.

• #2065 0598e83 Thanks @Andarist! - changeset publish now reads initial OTP values from npm and pnpm environment variables.

• #2171 3257f57 Thanks @beeequeue! - Enabled Node's Compile Cache to improve CLI startup speed.

• #1570 d099e43 Thanks @pralkarz! - Removed extra leftover code related to Changesets v1

• #2113 b8222e6 Thanks @Andarist! - Fixed accidental success logs on failed npm publishes

• #1616 609046c Thanks @bluwy! - Remove term-size dependency

• #1476 e0e1748 Thanks @pralkarz! - Replaced spawndamnit with tinyexec

• #584 6c79210 Thanks @Andarist! - Avoid an infinite loop when git commands fail to execute when Changesets try to retrieve commits that added files.

• #2177 b5e1762 Thanks @Andarist! - Avoid writing an undefined version when updating dependencies in unversioned private packages.

• #2163 5f8d925 Thanks @Andarist! - Update dependency ranges in the workspace root package.json.

• #2004 169b128 Thanks @ghostdevv! - Replace picocolors with node:util's styleText

• #1640 2ad65e0 Thanks @bluwy! - Remove deprecated flag warnings, including --updateChangelog, --isPublic, --skipCI, and --commit

• Updated dependencies [e0e1748, 6d1f384, a736a20, 062530b, 6a05002, ee10723, 88f2abb, c76b232, 6a05002, 694396c, d03ffc1, df424a4, b5e1762, c19b112, 03d4479, 162419d, b9407b3, 4c26f2f, 96b65ee, 3628cab, 8f7b607, db46911, b83787f, 2c7c043, 01f4da4, 813bbf3, 6a05002, c2348fc, fc42514, 062530b, 07278a7, c98af4c, df424a4, a0b5326, e0e1748, 6c79210, b5e1762, 3910adf, 5f8d925, 169b128, 18bc470, 6a05002, 3aae903, 062530b, 96b65ee]:

  • @changesets/apply-release-plan@8.0.0
  • @changesets/config@4.0.0
  • @changesets/write@1.0.0
  • @changesets/read@1.0.0
  • @changesets/git@4.0.0
  • @changesets/pre@3.0.0
  • @changesets/types@7.0.0
  • @changesets/errors@1.0.0
  • @changesets/assemble-release-plan@7.0.0
  • @changesets/get-dependents-graph@3.0.0
  • @changesets/should-skip-package@1.0.0
  • @changesets/changelog-git@1.0.0

Patch Changes

• Updated dependencies [68ea6ec, c98af4c]:
  • @changesets/config@4.0.0-next.10
  • @changesets/assemble-release-plan@7.0.0-next.11
  • @changesets/apply-release-plan@8.0.0-next.11

Major Changes

• #2190 96b65ee Thanks @bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset 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 in pre.json if certain changesets are deleted.

• #2186 3910adf Thanks @Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

Minor Changes

• #2135 fd7724a Thanks @youdie006! - Allow comma-separated values in array-valued CLI flags: the --major, --minor, and --patch flags of the add command, and the --ignore flag of the version command. For example, --minor pkg-a,pkg-b is now equivalent to --minor pkg-a --minor pkg-b. Surrounding whitespace is trimmed and empty entries are ignored.

Patch Changes

• Updated dependencies [96b65ee, 3910adf, 96b65ee]:
  • @changesets/apply-release-plan@8.0.0-next.10
  • @changesets/assemble-release-plan@7.0.0-next.10
  • @changesets/git@4.0.0-next.9
  • @changesets/pre@3.0.0-next.9
  • @changesets/read@1.0.0-next.10
  • @changesets/types@7.0.0-next.9
  • @changesets/config@4.0.0-next.9
  • @changesets/changelog-git@1.0.0-next.9
  • @changesets/get-dependents-graph@3.0.0-next.9
  • @changesets/should-skip-package@1.0.0-next.9
  • @changesets/write@1.0.0-next.9

Patch Changes

• #2159 15cf592 Thanks @ingvaldlorentzen! - Fixed already-published version detection with npm 12, which always wraps successful npm info --json output in an array. The unwrapped output made changeset publish treat every package as unpublished and fail attempting to republish existing versions.

Major Changes

• #2074 3599e47 Thanks @bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

Minor Changes

• #2068 d03ffc1 Thanks @bluwy! - Support {commit-short} placeholder for the snapshot.prereleaseTemplate config, which is a 7 character variant of {commit}

• #2061 c2db1dd Thanks @Andarist! - Added a changeset publish-plan command to inspect which packages would be published or tagged, with optional JSON output.

• #2100 90b4ad0 Thanks @Andarist! - Order releases into dependency-aware chunks so packages are grouped in publish order.

• #2063 ed77176 Thanks @Andarist! - Added changeset publish --from-pack-dir <dir> to publish packages from a previously created pack output directory.

• #2062 830443c Thanks @Andarist! - Added a changeset pack command that requires --out-dir and writes publishable package tarballs plus an enriched publish-plan.json into that directory, either from the current workspace or from a saved publish plan via --from-plan.

• #2073 b9cbd80 Thanks @bluwy! - Show if a package is private when selecting packages in changeset add

Patch Changes

• #2060 11bded4 Thanks @Andarist! - Fixed changeset publish to respect ignored packages for both publishing and private package tagging.

• #2064 ffd65fc Thanks @Andarist! - For pnpm projects, Changesets now match pnpm's native registry behavior more closely during unpublished package checks. Both scope-based publishConfig registry overrides and publishConfig.registry are now ignored.

• #2113 b8222e6 Thanks @Andarist! - Fixed publish error printing for pnpm 11.

• #2111 124ad07 Thanks @Andarist! - Auto-create the directory for the target publish plan file when executing changeset publish-plan --output <file>

• #2113 b8222e6 Thanks @Andarist! - Fixed accidental success logs on failed npm publishes

• #2091 3918fe5 Thanks @bluwy! - Log "New tag: ..." messages when running changeset publish to fix compatibility with the Changesets release GitHub action to create GitHub releases and push the new tags

• Updated dependencies [694396c, d03ffc1, 01f4da4, c2348fc]:

  • @changesets/apply-release-plan@8.0.0-next.6
  • @changesets/assemble-release-plan@7.0.0-next.6
  • @changesets/read@1.0.0-next.6

Major Changes

• #1860 92b1c1b Thanks @mixelburg! - changeset version now 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 --snapshot mode.

• #1954 ed6728c Thanks @beeequeue! - Bumped supported Node versions to ^22.11 || ^24 || >=26

• #1961 07278a7 Thanks @beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

• #1652 a0b5326 Thanks @bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

Minor Changes

• #1969 2c7c043 Thanks @marcalexiei! - Add a named export that mirrors the current default export

  The default export is slated for removal in the next major release, so this ensures a smoother transition path.

Patch Changes

• #1667 81832f8 Thanks @Andarist! - Fixed resolution of changelog and commit generator modules so built-in modules can still be loaded when they are not installed in the target project.

• Updated dependencies [81832f8, ed6728c, 03d4479, b9407b3, 2c7c043, 07278a7, ad3edbd, a0b5326]:

  • @changesets/apply-release-plan@8.0.0-next.3
  • @changesets/assemble-release-plan@7.0.0-next.3
  • @changesets/get-dependents-graph@3.0.0-next.3
  • @changesets/should-skip-package@1.0.0-next.3
  • @changesets/get-release-plan@5.0.0-next.3
  • @changesets/changelog-git@1.0.0-next.3
  • @changesets/config@4.0.0-next.3
  • @changesets/errors@1.0.0-next.2
  • @changesets/logger@1.0.0-next.2
  • @changesets/types@7.0.0-next.3
  • @changesets/write@1.0.0-next.3
  • @changesets/read@1.0.0-next.3
  • @changesets/git@4.0.0-next.3
  • @changesets/pre@3.0.0-next.3

Major Changes

• #1655 db46911 Thanks @bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

Minor Changes

• #1744 303cacd Thanks @beeequeue! - Bumped the default Prettier version used in the absence of the local installation to v3

Patch Changes

• #1875 12f20ea Thanks @beeequeue! - Replaced spawndamnit with tinyexec

• Updated dependencies [c19b112, db46911, 303cacd, 12f20ea]:

  • @changesets/types@7.0.0-next.2
  • @changesets/assemble-release-plan@7.0.0-next.2
  • @changesets/get-dependents-graph@3.0.0-next.2
  • @changesets/apply-release-plan@8.0.0-next.2
  • @changesets/get-release-plan@5.0.0-next.2
  • @changesets/config@4.0.0-next.2
  • @changesets/git@4.0.0-next.2
  • @changesets/pre@3.0.0-next.2
  • @changesets/changelog-git@1.0.0-next.2
  • @changesets/read@1.0.0-next.2
  • @changesets/should-skip-package@1.0.0-next.2
  • @changesets/write@1.0.0-next.2

Minor Changes

• #1889 96ca062 Thanks @mixelburg! - Error on unsupported flags for individual CLI commands and print the matching command usage to make mistakes easier to spot.

• #1873 42943b7 Thanks @mixelburg! - Respond to --help on all subcommands. Previously, --help was only handled when it was the sole argument; passing it alongside a subcommand (e.g. changeset version --help) would silently execute the command instead. Now --help always exits early and prints per-command usage when a known subcommand is provided, or the general help text otherwise.

Patch Changes

• d2121dc Thanks @Andarist! - Fix npm auth for path-based registries during publish by preserving configured registry URLs instead of normalizing them.

• #1888 036fdd4 Thanks @mixelburg! - Fix several changeset version issues with workspace protocol dependencies. Valid explicit workspace: ranges and aliases are no longer rewritten unnecessarily, and workspace path references are handled correctly during versioning.

• #1903 5c4731f Thanks @Andarist! - Gracefully handle stale npm info data leading to duplicate publish attempts.

• #1867 f61e716 Thanks @Andarist! - Improved detection for published state of prerelease-only packages without latest dist-tag on GitHub Packages registry.

• Updated dependencies [036fdd4, 036fdd4, 036fdd4]:

  • @changesets/assemble-release-plan@6.0.10
  • @changesets/get-dependents-graph@2.1.4
  • @changesets/apply-release-plan@7.1.1
  • @changesets/get-release-plan@4.0.16
  • @changesets/config@3.1.4