Update dependency @changesets/cli to ^2.27.1 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@changesets/cli (source)	^2.24.3 -> ^2.27.1

---

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.1

Compare Source

Patch Changes

• #​1267 86cfff1 Thanks @​Andarist! - Make ./bin.js available through package.json#exports to fix compatibility with changesets/action.

v2.27.0

Compare Source

Minor Changes

• #​1185 a971652 Thanks @​Andarist! - package.json#exports have been added to limit what (and how) code might be imported from the package.

• #​1236 dfd4cca Thanks @​camertron! - Avoid using short commit IDs

Patch Changes

• #​1053 90a870a Thanks @​paescuj! - Replace the dependency is-ci with ci-info.

• Updated dependencies [a971652, dfd4cca]:

  • @​changesets/assemble-release-plan@​6.0.0
  • @​changesets/get-dependents-graph@​2.0.0
  • @​changesets/apply-release-plan@​7.0.0
  • @​changesets/get-release-plan@​4.0.0
  • @​changesets/changelog-git@​0.2.0
  • @​changesets/config@​3.0.0
  • @​changesets/errors@​0.2.0
  • @​changesets/logger@​0.1.0
  • @​changesets/types@​6.0.0
  • @​changesets/write@​0.3.0
  • @​changesets/read@​0.6.0
  • @​changesets/git@​3.0.0
  • @​changesets/pre@​2.0.0

v2.26.2

Compare Source

Patch Changes

• #​1176 41988ce Thanks @​joshwooding! - Bump semver dependency to v7.5.3

• Updated dependencies [41988ce]:

  • @​changesets/apply-release-plan@​6.1.4
  • @​changesets/assemble-release-plan@​5.2.4
  • @​changesets/get-dependents-graph@​1.3.6
  • @​changesets/get-release-plan@​3.0.17
  • @​changesets/config@​2.3.1

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

• Updated dependencies [598136a, 521205d, 521205d, 598136a, 598136a, 521205d]:
  • @​changesets/git@​2.0.0
  • @​changesets/config@​2.3.0
  • @​changesets/types@​5.2.1
  • @​changesets/apply-release-plan@​6.1.3
  • @​changesets/read@​0.5.9
  • @​changesets/assemble-release-plan@​5.2.3
  • @​changesets/get-release-plan@​3.0.16
  • @​changesets/changelog-git@​0.1.14
  • @​changesets/get-dependents-graph@​1.3.5
  • @​changesets/pre@​1.0.14
  • @​changesets/write@​0.2.3

v2.25.2

Compare Source

Patch Changes

• Updated dependencies [6cc4300]:
  • @​changesets/apply-release-plan@​6.1.2
  • @​changesets/write@​0.2.2

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.

v2.25.0

Compare Source

Minor Changes

• #​662 8c08469 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

• #​953 98d63e0 Thanks @​alexamy! - Add a new line at the end of the default config file generated when invoking changeset init.

• #​949 64585ea 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:

  pkg-a - version: 1.0.0
  pkg-b - devDependencies['pkg-a']: 1.0.0
  pkg-c - dependencies['pkg-b']: 1.0.0
  

  With a changeset for pkg-a the pkg-c could have been sometimes incorrectly released.

• Updated dependencies [8c08469, 8c08469, 64585ea]:

  • @​changesets/git@​1.5.0
  • @​changesets/config@​2.2.0
  • @​changesets/types@​5.2.0
  • @​changesets/assemble-release-plan@​5.2.2
  • @​changesets/apply-release-plan@​6.1.1
  • @​changesets/read@​0.5.8
  • @​changesets/get-release-plan@​3.0.15
  • @​changesets/changelog-git@​0.1.13
  • @​changesets/get-dependents-graph@​1.3.4
  • @​changesets/pre@​1.0.13
  • @​changesets/write@​0.2.1

v2.24.4

Compare Source

Patch Changes

• Updated dependencies [c140171]:
  • @​changesets/apply-release-plan@​6.1.0
  • @​changesets/write@​0.2.0

---

Configuration

📅 Schedule: 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 has been generated by Mend Renovate. View repository job log here.