chore(deps): update dependency @changesets/cli to v2.31.1 - #18
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency @changesets/cli to v2.31.1#18renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
July 12, 2025 06:47
c089b02 to
6400248
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
August 10, 2025 14:23
6400248 to
140de3a
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
August 19, 2025 14:09
91f7f1f to
8197dc0
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
August 31, 2025 11:00
8197dc0 to
00e8aa0
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
September 9, 2025 14:32
00e8aa0 to
aedd29b
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
September 25, 2025 14:39
aedd29b to
eccdb4b
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
October 21, 2025 23:56
eccdb4b to
8a3ba34
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
November 11, 2025 00:10
8a3ba34 to
effd4a4
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
November 18, 2025 22:28
effd4a4 to
7c86c3c
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
December 3, 2025 17:54
d671c6e to
5acac34
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
December 31, 2025 20:01
8bb10bf to
2e87460
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
January 8, 2026 19:51
2e87460 to
7e0228d
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
January 19, 2026 14:44
7e0228d to
61a1e4d
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
February 2, 2026 14:56
61a1e4d to
04d389c
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
February 12, 2026 15:13
04d389c to
1b93713
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
March 3, 2026 13:29
1b93713 to
9cf382b
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
March 5, 2026 14:14
9cf382b to
8289693
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
March 14, 2026 20:22
8289693 to
203e310
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
April 8, 2026 16:45
9cf4b26 to
56ce8d6
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
April 17, 2026 22:11
56ce8d6 to
907f50d
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
April 29, 2026 10:59
907f50d to
64225fe
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
May 12, 2026 17:53
64225fe to
8aa128a
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
May 28, 2026 16:28
8aa128a to
05bdb82
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
June 11, 2026 19:57
05bdb82 to
8c32abd
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
July 16, 2026 08:48
86a3107 to
48c9cd9
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
July 20, 2026 22:35
48c9cd9 to
d2bf28b
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
August 12, 2026 00:33
d2bf28b to
c75cc0b
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
2.29.4→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]: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.