fix(deps): update dependency @changesets/cli to ^2.27.5

[renovate]

This PR contains the following updates:

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

---

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.5

Compare Source

Patch Changes

• #​1370 5e9d33a Thanks @​Andarist! - Fixed a regression that caused changeset version to fail on packages having a dev dependency on a skipped package.

• Updated dependencies [5e9d33a]:

  • @​changesets/get-dependents-graph@​2.1.0
  • @​changesets/assemble-release-plan@​6.0.2
  • @​changesets/config@​3.0.1
  • @​changesets/get-release-plan@​4.0.2
  • @​changesets/apply-release-plan@​7.0.3

v2.27.4

Compare Source

Patch Changes

• #​1361 954a16a Thanks @​jakebailey! - Ensure that version/tag do not touch private packages with when versioning/tagging is turned off using versionPackages config

• #​1369 d729d8c Thanks @​Andarist! - changeset tag should now correctly skip tags that exist on the remote

• Updated dependencies [954a16a]:

  • @​changesets/assemble-release-plan@​6.0.1
  • @​changesets/apply-release-plan@​7.0.2
  • @​changesets/get-release-plan@​4.0.1

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

• #​1354 69be7dc Thanks @​Andarist! - Fixed an issue with changeset status incorrectly returning an error status in two cases:

  • for changed ignored packages
  • for changed private packages when privatePackage.version was set to false

• #​1351 c6da182 Thanks @​TheHolyWaffle! - Fix an issue with not applying a custom .prettierrc configuration with prettier@>= 3.1.1

• Updated dependencies [c6da182]:

  • @​changesets/apply-release-plan@​7.0.1
  • @​changesets/write@​0.3.1

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

v2.24.3

Compare Source

Patch Changes

• Updated dependencies [b023e4b]:
  • @​changesets/assemble-release-plan@​5.2.1
  • @​changesets/get-release-plan@​3.0.14

v2.24.2

Compare Source

Patch Changes

• #​900 7d998ee Thanks @​sdirosa! - Fixed an issue with generating changelogs not being skipped when the changelog config option was set to false.

• #​720 0fd56e1 Thanks @​bhovhannes! - Private packages without a version field are no longer listed when adding a changeset.

• #​844 8627ec1 Thanks @​Andarist! - Attempt to log stdout when publish fails if stderr is empty and JSON error can't be retrieved from none of those.

• Updated dependencies [7d998ee, 7d998ee]:

  • @​changesets/config@​2.1.1
  • @​changesets/apply-release-plan@​6.0.4
  • @​changesets/get-release-plan@​3.0.13

v2.24.1

Compare Source

Patch Changes

• Updated dependencies [f64bc1b]:
  • @​changesets/git@​1.4.1
  • @​changesets/apply-release-plan@​6.0.3
  • @​changesets/read@​0.5.7
  • @​changesets/get-release-plan@​3.0.12

v2.24.0

Compare Source

Minor Changes

• #​858 dd9b76f Thanks @​dotansimha! - Added a new config flag for changesets version --snapshot mode: --snapshot-prerelease-template

• #​858 dd9b76f Thanks @​dotansimha! - Added a new config option: snapshot.prereleaseTemplate for customizing the way snapshot release numbers are being composed.

Patch Changes

• #​858 dd9b76f Thanks @​dotansimha! - A possibility to use the calculated version for snapshot releases is now stable 🥳 All snapshot-related config parameters are now grouped under a single config property called snapshot.

  To migrate, make sure to update your config.json.

  Old usage (still works, but comes with a deprecated warning):

  {
    "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
      "useCalculatedVersionForSnapshots": true
    }
  }

  New usage:

  {
    "snapshot": {
      "useCalculatedVersion": true
    }
  }

• Updated dependencies [dd9b76f, dd9b76f, dd9b76f]:

  • @​changesets/config@​2.1.0
  • @​changesets/git@​1.4.0
  • @​changesets/assemble-release-plan@​5.2.0
  • @​changesets/types@​5.1.0
  • @​changesets/apply-release-plan@​6.0.2
  • @​changesets/get-release-plan@​3.0.11
  • @​changesets/read@​0.5.6
  • @​changesets/changelog-git@​0.1.12
  • @​changesets/get-dependents-graph@​1.3.3
  • @​changesets/pre@​1.0.12
  • @​changesets/write@​0.1.9

v2.23.2

Compare Source

Patch Changes

• #​871 e174172 Thanks @​NicoKam! - Fixed filtering of the ignored packages when adding a changeset.

v2.23.1

Compare Source

Patch Changes

• #​843 101b1cb Thanks @​caohuilin! - Fixed the printed filename in the verbose output of changeset status.

• #​857 7febb59 Thanks @​dotansimha! - Fixed an issue with dependency ranges still using pre-existing range modifiers instead of fixed package versions when performing a snapshot release. This ensures that installs of snapshot versions are always reproducible.

• #​744 84e46d1 Thanks @​mskelton! - Ignored packages are no longer listed when adding a changeset.

• Updated dependencies [2827c7a, 7b1c0c1, 7febb59]:

  • @​changesets/config@​2.0.1
  • @​changesets/apply-release-plan@​6.0.1
  • @​changesets/get-release-plan@​3.0.10

v2.23.0

Compare Source

Minor Changes

• #​796 745b771 Thanks @​JakeGinnivan! - Upgraded tty-table to fix deprecation warnings coming from its transitive dependency.

Patch Changes

• #​811 c54c25d Thanks @​samrose3! - Improved accessibility of the CLI prompts by using selected/unselected indicators that don't rely solely on the colors.

• #​767 d6bfcc5 Thanks @​Andarist! - Improve the error message when a package referenced in a changeset can't be found. The message will now also include the changeset's ID.

• Updated dependencies [d6bfcc5]:

  • @​changesets/assemble-release-plan@​5.1.3
  • @​changesets/get-release-plan@​3.0.9

v2.22.0

Compare Source

Minor Changes

• #​768 c87eba6 Thanks @​rohit-gohri! - Allow "commit" option to be more configurable. You can now point to a module (using a module name or a relative path) that might contain getAddMessage and/or getVersionMessage. This allows you to configure how the commit message is generated, if [skip ci] gets included, etc.

Patch Changes

• #​776 ad7506d Thanks @​janosh! - changeset init will now configure baseBranch: "main" in the .changeset/config.json as the default value.

• #​770 eb86652 Thanks @​alizeait! - changeset add and changeset status should now properly handle the situation where Changesets are managed from a directory different than the root of the repository.

• Updated dependencies [c87eba6, eb86652, c87eba6, c87eba6]:

  • @​changesets/types@​5.0.0
  • @​changesets/git@​1.3.2
  • @​changesets/apply-release-plan@​6.0.0
  • @​changesets/config@​2.0.0
  • @​changesets/assemble-release-plan@​5.1.2
  • @​changesets/changelog-git@​0.1.11
  • @​changesets/get-dependents-graph@​1.3.2
  • @​changesets/get-release-plan@​3.0.8
  • @​changesets/pre@​1.0.11
  • @​changesets/read@​0.5.5
  • @​changesets/write@​0.1.8

---

Configuration

📅 Schedule: Branch creation - "before 10am on the first day of the month" in timezone GMT, 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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3f8ac57

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