chore(deps): update dependency @changesets/cli to v2.31.1#84
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency @changesets/cli to v2.31.1#84renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #84 +/- ##
=======================================
Coverage 31.74% 31.74%
=======================================
Files 10 10
Lines 419 419
Branches 22 22
=======================================
Hits 133 133
Misses 281 281
Partials 5 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
August 10, 2025 13:39
bac4669 to
27903b6
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
August 19, 2025 19:01
733d400 to
78052dc
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
August 31, 2025 12:32
78052dc to
3357cac
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
September 9, 2025 17:12
3357cac to
88dfe46
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
September 25, 2025 21:11
88dfe46 to
9ca2583
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
October 21, 2025 09:10
9ca2583 to
ac0a202
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
November 10, 2025 17:03
ac0a202 to
c24ced5
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
November 18, 2025 19:52
c24ced5 to
77406b5
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
December 3, 2025 17:45
d174ae4 to
96ced1f
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
December 31, 2025 13:00
96ced1f to
fad1ede
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
January 8, 2026 17:29
fad1ede to
2f13eb5
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
January 23, 2026 18:50
5267b3d to
cf76b87
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
February 12, 2026 18:01
cf76b87 to
04c5b66
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
March 3, 2026 14:32
04c5b66 to
e2e6de4
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
April 1, 2026 17:51
e2e6de4 to
4a36968
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
April 17, 2026 21:32
4a36968 to
cd86092
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
May 12, 2026 15:43
cd86092 to
05614e4
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
2 times, most recently
from
June 1, 2026 16:46
67b69a1 to
768372b
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
June 11, 2026 20:59
768372b to
d5d34a5
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
July 12, 2026 13:12
d5d34a5 to
da34c8c
Compare
renovate
Bot
force-pushed
the
renovate/changesets-cli-2.x-lockfile
branch
from
July 16, 2026 09:05
da34c8c to
908c9e0
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
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.