Skip to content

chore(deps): update dependency @changesets/cli to v2.31.1 - #19

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/changesets-cli-2.x-lockfile
Open

chore(deps): update dependency @changesets/cli to v2.31.1#19
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/changesets-cli-2.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Mar 3, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@changesets/cli (source) 2.29.82.31.1 age adoption passing confidence

Release Notes

changesets/changesets (@​changesets/cli)

v2.31.1

Compare Source

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.

v2.31.0

Compare Source

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

v2.30.0

Compare Source

Minor Changes
  • #​1840 057cca2 Thanks @​wotan-allfather! - Add --since flag to add command

    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.

  • #​1845 2b4a66a 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.

  • #​1774 667fe5a 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.

  • #​1839 73b1809 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.

  • #​1806 0e8e01e 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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented Mar 3, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 77f84d5

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x-lockfile branch from 5b18659 to 34eaf37 Compare April 8, 2026 23:48
@renovate renovate Bot changed the title chore(deps): update dependency @changesets/cli to v2.30.0 chore(deps): update dependency @changesets/cli to v2.31.0 Apr 19, 2026
@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x-lockfile branch from 34eaf37 to 606ce09 Compare April 19, 2026 05:50
@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x-lockfile branch from 606ce09 to 2a46f87 Compare May 13, 2026 03:03
@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x-lockfile branch 2 times, most recently from 16f000b to 2da56a2 Compare June 5, 2026 07:40
@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x-lockfile branch from 2da56a2 to 5b5a678 Compare June 12, 2026 15:57
@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x-lockfile branch from 5b5a678 to 94a70a6 Compare July 15, 2026 04:02
@renovate renovate Bot changed the title chore(deps): update dependency @changesets/cli to v2.31.0 chore(deps): update dependency @changesets/cli to v2.31.1 Jul 18, 2026
@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x-lockfile branch from 94a70a6 to 4c40957 Compare July 18, 2026 10:47
@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x-lockfile branch from 4c40957 to 77f84d5 Compare August 1, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants