Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@changesets/cli (source) 2.25.02.31.1 age confidence
@changesets/cli (source) 2.29.82.31.1 age 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

v2.29.8

Compare Source

Patch Changes

v2.29.7

Compare Source

Patch Changes

v2.29.6

Compare Source

Patch Changes

v2.29.5

Compare Source

Patch Changes

v2.29.4

Compare Source

Patch Changes

v2.29.3

Compare Source

Patch Changes

v2.29.2

Compare Source

Patch Changes

v2.29.1

Compare Source

Patch Changes

v2.29.0

Compare Source

Minor Changes

v2.28.1

Compare Source

Patch Changes

v2.28.0

Compare Source

Minor Changes
Patch Changes

v2.27.12

Compare Source

Patch Changes

v2.27.11

Compare Source

Patch Changes

v2.27.10

Compare Source

Patch Changes

v2.27.9

Compare Source

Patch Changes

v2.27.8

Compare Source

Patch Changes

v2.27.7

Compare Source

Patch Changes

v2.27.6

Compare Source

Patch Changes

v2.27.5

Compare Source

Patch Changes

v2.27.4

Compare Source

Patch Changes

v2.27.3

Compare Source

Patch Changes
  • #​1357 18c966a 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.

v2.27.2

Compare Source

Patch Changes

v2.27.1

Compare Source

Patch Changes

v2.27.0

Compare Source

Minor Changes
Patch Changes

v2.26.2

Compare Source

Patch Changes

v2.26.1

Compare Source

Patch Changes
  • #​1115 feddc88 Thanks @​Andarist! - Call pnpm publish directly from the directory of the published package. This allows pnpm to correctly handle configured publishConfig.directory.

v2.26.0

Compare Source

Minor Changes
  • #​1033 521205d Thanks @​Andarist! - A new config-level changedFilePatterns option has been added. You can configure it with an array of glob patterns like here:

    // .changeset/config.json
    {
      "changedFilePatterns": ["src/**"]
    }

    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.

Patch Changes

v2.25.2

Compare Source

Patch Changes

v2.25.1

Compare Source

Patch Changes
  • #​997 4d4d67b Thanks @​JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet

  • #​985 8d0115e Thanks @​mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite the privatePackages.version: false setting.


Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled because a matching PR was automerged previously.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

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

@renovate

renovate Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: site/study/2026/experiments/environments/1618/yarn.lock

File name: site/study/2026/experiments/environments/1617/yarn.lock

@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x branch 2 times, most recently from bee94fc to db3893c Compare September 12, 2026 05:20
@renovate
renovate Bot force-pushed the renovate/changesets-cli-2.x branch from db3893c to 0e2b3b9 Compare September 15, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants