You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(deps): update dependency @changesets/cli to v2.31.1 - #409
#215915cf592 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.
#188996ca062 Thanks @mixelburg! - Error on unsupported flags for individual CLI commands and print the matching command usage to make mistakes easier to spot.
#187342943b7 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.
#1888036fdd4 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.
#19035c4731f Thanks @Andarist! - Gracefully handle stale npm info data leading to duplicate publish attempts.
#1867f61e716 Thanks @Andarist! - Improved detection for published state of prerelease-only packages without latest dist-tag on GitHub Packages registry.
The add command now supports a --since flag that allows you to specify which branch, tag, or git ref to use when detecting changed packages. This is useful for gitflow workflows where you have multiple target branches and the baseBranch config option doesn't cover all use cases.
Example: changeset add --since=develop
If not provided, the command falls back to the baseBranch value in your .changeset/config.json.
#18452b4a66a Thanks @Andarist! - Delegate OTP prompting to the package manager instead of handling it in-process. This allows Changesets to use the package manager's native web auth support.
#1774667fe5a Thanks @bluwy! - Support importing custom commit option ES module. Previously, it used require() which only worked for CJS modules, however now it uses import() which supports both CJS and ES modules.
#183973b1809 Thanks @leochiu-a! - Add a --message (-m) flag to changeset add (and default changeset) so the changeset summary can be provided from the command line. When --message is present, the summary prompt is skipped while the final confirmation step is kept.
#18060e8e01e Thanks @luisadame! - Changeset CLI can now be run from the nested directories in the project, where the .changeset directory has to be found in one of the parent directories
Patch Changes
#18499dc3230 Thanks @Andarist! - Compute the terminal's size lazily to avoid spurious stderr output in non-interactive mode
#18572a73025 Thanks @mixelburg! - Fix confusing prompt labels when entering changeset summary after external editor fallback
#18426df3a5e Thanks @RodrigoHamuy! - Allow private packages to depend on skipped packages without requiring them to also be skipped. Private packages are not published to npm, so it is safe for them to have dependencies on ignored or unversioned packages.
#1776503fcaa Thanks @bluwy! - Support absolute paths in changeset status --output <path>
#16936352819 Thanks @Andarist! - Fixed an issue with workspace:^ and workspace:~ dependency ranges not being semantically treated as, respectively, ^CURRENT_VERSION and ~CURRENT_VERSION. This led to dependent packages being, at times, bumped too often when their dependencies with those ranges were bumped.
#1361954a16a Thanks @jakebailey! - Version 2.25.0 introduced the privatePackage configuration option with default { version: false, tag: false }; due to a bug, these options were not respected in all commands, leading to commands like changeset tag still tagging private packages. This has been fixed, and all packages now respect this option.
#1369d729d8c Thanks @Andarist! - changeset tag should now correctly skip tags that exist on the remote
#135718c966a Thanks @Andarist! - Fixed an issue with changeset status executed without since argument. It should now correctly use the configured base branch as the default value.
#1115feddc88 Thanks @Andarist! - Call pnpm publish directly from the directory of the published package. This allows pnpm to correctly handle configured publishConfig.directory.
#1033521205d Thanks @Andarist! - A new config-level changedFilePatterns option has been added. You can configure it with an array of glob patterns like here:
Files that do not match the configured pattern won't contribute to the "changed" status of the package to which they belong. This both affects changesets add and changeset status.
#9974d4d67b Thanks @JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet
#9858d0115e Thanks @mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite the privatePackages.version: false setting.
#6628c08469 Thanks @JakeGinnivan! - Private packages can now be tagged in the same way public packages do when they are published to npm.
To enable set privatePackages: { version: true, tag: true } in your config.json.
You can also now opt private packages out of versioning entirely by setting privatePackages: false.
Patch Changes
#95398d63e0 Thanks @alexamy! - Add a new line at the end of the default config file generated when invoking changeset init.
#94964585ea Thanks @Andarist, @BPScott! - Fixed the issue that caused transitive dependents of dev dependents to be bumped when a package got bumped and when using ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.updateInternalDependents: "always". To illustrate this with an example:
#858dd9b76f Thanks @dotansimha! - Added a new config flag for changesets version --snapshot mode: --snapshot-prerelease-template
#858dd9b76f Thanks @dotansimha! - Added a new config option: snapshot.prereleaseTemplate for customizing the way snapshot release numbers are being composed.
Patch Changes
#858dd9b76f Thanks @dotansimha! - A possibility to use the calculated version for snapshot releases is now stable 🥳 All snapshot-related config parameters are now grouped under a single config property called snapshot.
To migrate, make sure to update your config.json.
Old usage (still works, but comes with a deprecated warning):
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
2.9.1→2.31.1Release Notes
changesets/changesets (@changesets/cli)
v2.31.1Compare Source
Patch Changes
15cf592Thanks @ingvaldlorentzen! - Fixed already-published version detection with npm 12, which always wraps successfulnpm info --jsonoutput in an array. The unwrapped output madechangeset publishtreat every package as unpublished and fail attempting to republish existing versions.v2.31.0Compare Source
Minor Changes
#1889
96ca062Thanks @mixelburg! - Error on unsupported flags for individual CLI commands and print the matching command usage to make mistakes easier to spot.#1873
42943b7Thanks @mixelburg! - Respond to--helpon all subcommands. Previously,--helpwas 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--helpalways exits early and prints per-command usage when a known subcommand is provided, or the general help text otherwise.Patch Changes
d2121dcThanks @Andarist! - Fix npm auth for path-based registries during publish by preserving configured registry URLs instead of normalizing them.#1888
036fdd4Thanks @mixelburg! - Fix severalchangeset versionissues with workspace protocol dependencies. Valid explicitworkspace:ranges and aliases are no longer rewritten unnecessarily, and workspace path references are handled correctly during versioning.#1903
5c4731fThanks @Andarist! - Gracefully handle stalenpm infodata leading to duplicate publish attempts.#1867
f61e716Thanks @Andarist! - Improved detection forpublishedstate of prerelease-only packages withoutlatestdist-tag on GitHub Packages registry.Updated dependencies [
036fdd4,036fdd4,036fdd4]:v2.30.0Compare Source
Minor Changes
#1840
057cca2Thanks @wotan-allfather! - Add--sinceflag toaddcommandThe
addcommand now supports a--sinceflag that allows you to specify which branch, tag, or git ref to use when detecting changed packages. This is useful for gitflow workflows where you have multiple target branches and thebaseBranchconfig option doesn't cover all use cases.Example:
changeset add --since=developIf not provided, the command falls back to the
baseBranchvalue in your.changeset/config.json.#1845
2b4a66aThanks @Andarist! - Delegate OTP prompting to the package manager instead of handling it in-process. This allows Changesets to use the package manager's native web auth support.#1774
667fe5aThanks @bluwy! - Support importing customcommitoption ES module. Previously, it usedrequire()which only worked for CJS modules, however now it usesimport()which supports both CJS and ES modules.#1839
73b1809Thanks @leochiu-a! - Add a--message(-m) flag tochangeset add(and defaultchangeset) so the changeset summary can be provided from the command line. When--messageis present, the summary prompt is skipped while the final confirmation step is kept.#1806
0e8e01eThanks @luisadame! - Changeset CLI can now be run from the nested directories in the project, where the.changesetdirectory has to be found in one of the parent directoriesPatch Changes
#1849
9dc3230Thanks @Andarist! - Compute the terminal's size lazily to avoid spurious stderr output in non-interactive mode#1857
2a73025Thanks @mixelburg! - Fix confusing prompt labels when entering changeset summary after external editor fallback#1842
6df3a5eThanks @RodrigoHamuy! - Allow private packages to depend on skipped packages without requiring them to also be skipped. Private packages are not published to npm, so it is safe for them to have dependencies on ignored or unversioned packages.#1776
503fcaaThanks @bluwy! - Support absolute paths inchangeset status --output <path>Updated dependencies [
667fe5a,1772598,b6f4c74,6df3a5e,6df3a5e,27fd8f4]:v2.29.8Compare Source
Patch Changes
#1437
aa68d54Thanks @with-heart! - Tweaked a hint text printed when one confirms an empty set of packages to be releasedUpdated dependencies [
cc28222,e520bf5,13dace8]:v2.29.7Compare Source
Patch Changes
957f24e]:v2.29.6Compare Source
Patch Changes
a3563b0Thanks @benmccann! - Switch to maintained fork ofexternal-editorv2.29.5Compare Source
Patch Changes
#1693
6352819Thanks @Andarist! - Fixed an issue withworkspace:^andworkspace:~dependency ranges not being semantically treated as, respectively,^CURRENT_VERSIONand~CURRENT_VERSION. This led to dependent packages being, at times, bumped too often when their dependencies with those ranges were bumped.Updated dependencies [
6352819]:v2.29.4Compare Source
Patch Changes
#1668
65d6632Thanks @Andarist! - Fixed a crash in pre mode when trying to version private packages when tagging for private package is disabledUpdated dependencies [
65d6632]:v2.29.3Compare Source
Patch Changes
#1589
de8bebcThanks @remorses, @vzt7! - Fixed a crash in prerelease mode when a package misses the version field in itspackage.json#1619
c1e8a78Thanks @manucorporat! - Support../inpublishConfig.directorywhen publishing packagesUpdated dependencies [
de8bebc]:v2.29.2Compare Source
Patch Changes
#1636
f73f84aThanks @Netail! - Correctly resolve new changesets withsinceoption when the.changesetdirectory is not directly in the git rootUpdated dependencies [
f73f84a]:v2.29.1Compare Source
Patch Changes
#1620
b15e629Thanks @Netail! - Correctly fetch new changesets with since if the git option diff.relative has been set to trueUpdated dependencies [
b15e629]:v2.29.0Compare Source
Minor Changes
29f34a3Thanks @JounQin! - Support scoped registries configured usingpackage.json#publishConfigv2.28.1Compare Source
Patch Changes
b9df596]:v2.28.0Compare Source
Minor Changes
84a4a1bThanks @bennypowers! - Added a new config option to opt-out from formatting with Prettier usingprettier: false.Patch Changes
84a4a1b,84a4a1b]:v2.27.12Compare Source
Patch Changes
#1562
a0f87f1Thanks @Netail, @cefn! - Fixed changelog application when executing usingnpxand similar toolsUpdated dependencies [
a0f87f1]:v2.27.11Compare Source
Patch Changes
f0270f6]:v2.27.10Compare Source
Patch Changes
#1485
baf5644Thanks @bluwy! - Ignore error if failed to find changed packages inchangeset add#1489
7bf751cThanks @marcalexiei! - Use custom errors when exiting add command due to missing tool#1466
ccce743Thanks @marcalexiei! - Add error message and exit when there are no versionable packages#1514
962ab91Thanks @nicoalonsop! - Update spawndamnit to fix cross-spawn vulnerabilityUpdated dependencies [
7323704,26c8ba9,82cacb2,962ab91]:v2.27.9Compare Source
Patch Changes
#1458
400ab7bThanks @benmccann! - Moved@types/semvertodevDependencies#1462
689e541Thanks @benmccann! - removeoutdentdependencyv2.27.8Compare Source
Patch Changes
#1417
bc75c1aThanks @trivikr! - Replacechalkwithpicocolorsto reduce install size#1419
4efc038Thanks @bluwy! - Fix logging--versionflag#1445
52c302aThanks @bluwy! - Remove unused@babel/runtimedependency#1446
5150fc1Thanks @benmccann! - Switched frompreferred-pmtopackage-manager-detectorin order to reduce installation sizeUpdated dependencies [
bc75c1a,52c302a]:v2.27.7Compare Source
Patch Changes
#1047
d108fa6Thanks @patzick! - Fixed a crash that could occur when depending on a tagged version of another workspace package.#1400
dd6e5bbThanks @Andarist! - Fixed a crash that prevented the CLI from running in a scenario when a workspace depends on the root workspaceUpdated dependencies [
d108fa6,dd6e5bb,dd6e5bb]:v2.27.6Compare Source
Patch Changes
#1392
f295b3eThanks @bluwy! - Replacemeowdependency withmrito reduce the number of transitive dependencies#1390
6a3452eThanks @bluwy! - Displaychangeset status --verbosein list form and removetty-tabledependencyv2.27.5Compare Source
Patch Changes
#1370
5e9d33aThanks @Andarist! - Fixed a regression that causedchangeset versionto fail on packages having a dev dependency on a skipped package.Updated dependencies [
5e9d33a]:v2.27.4Compare Source
Patch Changes
#1361
954a16aThanks @jakebailey! - Version 2.25.0 introduced theprivatePackageconfiguration option with default{ version: false, tag: false }; due to a bug, these options were not respected in all commands, leading to commands likechangeset tagstill tagging private packages. This has been fixed, and all packages now respect this option.#1369
d729d8cThanks @Andarist! -changeset tagshould now correctly skip tags that exist on the remoteUpdated dependencies [
954a16a]:v2.27.3Compare Source
Patch Changes
18c966aThanks @Andarist! - Fixed an issue withchangeset statusexecuted withoutsinceargument. It should now correctly use the configured base branch as the default value.v2.27.2Compare Source
Patch Changes
#1354
69be7dcThanks @Andarist! - Fixed an issue withchangeset statusincorrectly returning an error status in two cases:privatePackage.versionwas set tofalse#1351
c6da182Thanks @TheHolyWaffle! - Fix an issue with not applying a custom.prettierrcconfiguration withprettier@>= 3.1.1Updated dependencies [
c6da182]:v2.27.1Compare Source
Patch Changes
#1562
a0f87f1Thanks @Netail, @cefn! - Fixed changelog application when executing usingnpxand similar toolsUpdated dependencies [
a0f87f1]:v2.27.0Compare Source
Minor Changes
#1185
a971652Thanks @Andarist! -package.json#exportshave been added to limit what (and how) code might be imported from the package.#1236
dfd4ccaThanks @camertron! - Avoid using short commit IDsPatch Changes
#1053
90a870aThanks @paescuj! - Replace the dependencyis-ciwithci-info.Updated dependencies [
a971652,dfd4cca]:v2.26.2Compare Source
Patch Changes
#1176
41988ceThanks @joshwooding! - Bumpsemverdependency to v7.5.3Updated dependencies [
41988ce]:v2.26.1Compare Source
Patch Changes
feddc88Thanks @Andarist! - Callpnpm publishdirectly from the directory of the published package. This allowspnpmto correctly handle configuredpublishConfig.directory.v2.26.0Compare Source
Minor Changes
#1033
521205dThanks @Andarist! - A new config-levelchangedFilePatternsoption has been added. You can configure it with an array of glob patterns like here:Files that do not match the configured pattern won't contribute to the "changed" status of the package to which they belong. This both affects
changesets addandchangeset status.Patch Changes
598136a,521205d,521205d,598136a,598136a,521205d]:v2.25.2Compare Source
Patch Changes
6cc4300]:v2.25.1Compare Source
Patch Changes
#997
4d4d67bThanks @JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet#985
8d0115eThanks @mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite theprivatePackages.version: falsesetting.v2.25.0Compare Source
Minor Changes
#662
8c08469Thanks @JakeGinnivan! - Private packages can now be tagged in the same way public packages do when they are published to npm.To enable set
privatePackages: { version: true, tag: true }in your config.json.You can also now opt private packages out of versioning entirely by setting
privatePackages: false.Patch Changes
#953
98d63e0Thanks @alexamy! - Add a new line at the end of the default config file generated when invokingchangeset init.#949
64585eaThanks @Andarist, @BPScott! - Fixed the issue that caused transitive dependents of dev dependents to be bumped when a package got bumped and when using___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.updateInternalDependents: "always". To illustrate this with an example:With a changeset for
pkg-athepkg-ccould have been sometimes incorrectly released.Updated dependencies [
8c08469,8c08469,64585ea]:v2.24.4Compare Source
Patch Changes
c140171]:v2.24.3Compare Source
Patch Changes
b023e4b]:v2.24.2Compare Source
Patch Changes
#900
7d998eeThanks @sdirosa! - Fixed an issue with generating changelogs not being skipped when thechangelogconfig option was set tofalse.#720
0fd56e1Thanks @bhovhannes! - Private packages without aversionfield are no longer listed when adding a changeset.#844
8627ec1Thanks @Andarist! - Attempt to logstdoutwhen publish fails ifstderris empty and JSON error can't be retrieved from none of those.Updated dependencies [
7d998ee,7d998ee]:v2.24.1Compare Source
Patch Changes
f64bc1b]:v2.24.0Compare Source
Minor Changes
#858
dd9b76fThanks @dotansimha! - Added a new config flag forchangesets version --snapshotmode:--snapshot-prerelease-template#858
dd9b76fThanks @dotansimha! - Added a new config option:snapshot.prereleaseTemplatefor customizing the way snapshot release numbers are being composed.Patch Changes
#858
dd9b76fThanks @dotansimha! - A possibility to use the calculated version for snapshot releases is now stable 🥳 All snapshot-related config parameters are now grouped under a single config property calledsnapshot.To migrate, make sure to update your
config.json.Old usage (still works, but comes with a deprecated warning):
{ "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": { "useCalculatedVersionForSnapshots": true } }New usage:
{ "snapshot": { "useCalculatedVersion": true } }Updated dependencies [
dd9b76f,dd9b76f,dd9b76f]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.