Update dependency @changesets/cli to ^2.26.2 #24
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.14.1->^2.26.2Release Notes
changesets/changesets (@changesets/cli)
v2.26.2Compare Source
Patch Changes
#1176
41988ceThanks @joshwooding! - Bumpsemverdependency to v7.5.3Updated dependencies [
41988ce]:v2.26.1Compare Source
Patch Changes
feddc88Thanks @Andarist! - Callpnpm publishdirectly from the directory of the published package. This allowspnpmto correctly handle configuredpublishConfig.directory.v2.26.0Compare Source
Minor Changes
#1033
521205dThanks @Andarist! - A new config-levelchangedFilePatternsoption has been added. You can configure it with an array of glob patterns like here: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 addandchangeset status.Patch Changes
598136a,521205d,521205d,598136a,598136a,521205d]:v2.25.2Compare Source
Patch Changes
6cc4300]:v2.25.1Compare Source
Patch Changes
#997
4d4d67bThanks @JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet#985
8d0115eThanks @mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite theprivatePackages.version: falsesetting.v2.25.0Compare Source
Minor Changes
#662
8c08469Thanks @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
98d63e0Thanks @alexamy! - Add a new line at the end of the default config file generated when invokingchangeset init.#949
64585eaThanks @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:With a changeset for
pkg-athepkg-ccould have been sometimes incorrectly released.Updated dependencies [
8c08469,8c08469,64585ea]:v2.24.4Compare Source
Patch Changes
c140171]:v2.24.3Compare Source
Patch Changes
b023e4b]:v2.24.2Compare Source
Patch Changes
#900
7d998eeThanks @sdirosa! - Fixed an issue with generating changelogs not being skipped when thechangelogconfig option was set tofalse.#720
0fd56e1Thanks @bhovhannes! - Private packages without aversionfield are no longer listed when adding a changeset.#844
8627ec1Thanks @Andarist! - Attempt to logstdoutwhen publish fails ifstderris empty and JSON error can't be retrieved from none of those.Updated dependencies [
7d998ee,7d998ee]:v2.24.1Compare Source
Patch Changes
f64bc1b]:v2.24.0Compare Source
Minor Changes
#858
dd9b76fThanks @dotansimha! - Added a new config flag forchangesets version --snapshotmode:--snapshot-prerelease-template#858
dd9b76fThanks @dotansimha! - Added a new config option:snapshot.prereleaseTemplatefor customizing the way snapshot release numbers are being composed.Patch Changes
#858
dd9b76fThanks @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 calledsnapshot.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]:v2.23.2Compare Source
Patch Changes
e174172Thanks @NicoKam! - Fixed filtering of the ignored packages when adding a changeset.v2.23.1Compare Source
Patch Changes
#843
101b1cbThanks @caohuilin! - Fixed the printed filename in the verbose output ofchangeset status.#857
7febb59Thanks @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
84e46d1Thanks @mskelton! - Ignored packages are no longer listed when adding a changeset.Updated dependencies [
2827c7a,7b1c0c1,7febb59]:v2.23.0Compare Source
Minor Changes
745b771Thanks @JakeGinnivan! - Upgradedtty-tableto fix deprecation warnings coming from its transitive dependency.Patch Changes
#811
c54c25dThanks @samrose3! - Improved accessibility of the CLI prompts by using selected/unselected indicators that don't rely solely on the colors.#767
d6bfcc5Thanks @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]:v2.22.0Compare Source
Minor Changes
c87eba6Thanks @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 containgetAddMessageand/orgetVersionMessage. This allows you to configure how the commit message is generated, if[skip ci]gets included, etc.Patch Changes
#776
ad7506dThanks @janosh! -changeset initwill now configurebaseBranch: "main"in the.changeset/config.jsonas the default value.#770
eb86652Thanks @alizeait! -changeset addandchangeset statusshould 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]:v2.21.1Compare Source
Patch Changes
#760
5a2a59aThanks @Andarist! - Fixed an issue with logging non-stringified Buffers in case of publish errors.#769
3e8e672Thanks @Andarist! - Fixed an infinite loop involving a fixed group of packages and a package within that group that was both ignored and dependent on another package from that group.Updated dependencies [
3e8e672]:v2.21.0Compare Source
Minor Changes
#690
27a5a82Thanks @Andarist! - Added a new.changeset/config.jsonoption:fixed. It can be used to group packages that should always be released together. If any package from a group is going to be released then all packages from that group will be released together (with the same version).This is similar to what people often know from Lerna as this is how their fixed/locked mode works.
Patch Changes
#706
0812858Thanks @Andarist! - Fixed an issue with"none"releases causing package versions being bumped during snapshot releases. In addition to when you create"none"release types explicitly Changesets might create them implicitly in some situations, for example under some circumstances this issue caused snapshot releases to be created sometimes for ignored packages.#703
15c461dThanks @Andarist! - Fixed an issue with*dependency ranges not being replaced in premode. Those have to replaced with exact versions because prereleases don't satisfy wildcard ranges. A published prerelease package with such dependency range left untouched won't install correct prerelease dependency version.#749
d14cf79Thanks @Andarist! - Fixed an issue that caused created CHANGELOG files not being formatted in the same way as the updated ones (this could happen when callingchangeset versionfor the very first time for a package).#751
59c7ebcThanks @Rugvip! - Fixed an issue where dependent packages would sometimes not get bumped properly when exiting prerelease mode.#703
15c461dThanks @Andarist! - Fixed an issue with dependant packages being always bumped when their*dependency was bumped.Updated dependencies [
0812858,15c461d,27a5a82,27a5a82,d14cf79,27a5a82,0d1debd,59c7ebc,15c461d]:v2.20.0Compare Source
Minor Changes
#698
9e14a9aThanks @zthxxx! - Reworked the CLI output when adding a changeset. This includes fixing broken formatting in certain terminal width, reducing visual noise and making other small adjustments.#704
6f9c9d6Thanks @Andarist! - Dependencies specified using a tag will no longer result in printing incorrect errors in the console.Patch Changes
#740
957e39cThanks @akphi! - Fixed an issue with failing to parse changesets containing a completely empty summary.#693
1be201fThanks @luciaquirke! - Fixed an issue withnonerelease type sometimes overriding other release types and thus preventing a release from happening.Updated dependencies [
6f9c9d6,77c1cef,1be201f]:v2.19.0Compare Source
Minor Changes
b9b6453Thanks @Andarist! - Added support for a--no-git-tagCLI flag that can be used withchangeset publishto skip creating git tags for published packages. This is mostly useful when publishing snapshot releases.Patch Changes
#713
82be80eThanks @zthxxx! - Fixed an issue with not being able to reenter exited pre mode.#708
ab8f2b2Thanks @Andarist! - Updatedis-cidependency that helps us to check if Changesets are executed in the CI environment.#710
4272cb0Thanks @Andarist! - Errors received fromnpm profile get --json, that is used to check if 2FA is required, will now always be printed.Updated dependencies [
82be80e,e4c4b29]:v2.18.1Compare Source
Patch Changes
#676
d8f0e68Thanks @Andarist! - Improved compatibility with npm 7+ since they've started to print errors to thestderr(where previously they were printed tostdout) when usingnpm publish --json.#676
d8f0e68Thanks @Andarist! - Fixed an internal issue that preventednpm publish --json's output to be handled properly. This makes sure that unrelated JSONs printed by lifecycle scripts don't interfere with our logic.#667
fe8db75Thanks @fz6m! - Upgraded@manypkg/get-packagesdependency to fix getting correct packages in pnpm workspaces with exclude rules.Updated dependencies [
fe8db75,9a993ba]:v2.18.0Compare Source
Minor Changes
#634
2b49c39Thanks @joeldenning! - The newchangeset tagcommand has been added. It can be used to create git tags for all packages.This is helpful in situations where a different tool is used to publish packages instead of Changesets. For situations where
changeset publishis executed, runningchangeset tagis not needed.Note that it is expected that
changeset versionis run beforechangeset tag, so that thepackage.jsonversions are updated before the git tags are created. This command also doesn't take any configuration into account - it simply create tags for all packages with whatever version that is currently in their respectivepackage.json.Patch Changes
#585
74dda8cThanks @javier-garcia-meteologica! - Add support forworkspace:^andworkspace:~dependency ranges.#660
5413f3eThanks @tmkx! - Fixed an issue with adding[undefined]to the generated changelog when the commit adding a changeset file could not be found. This could have happened when runningchangeset add && changeset versionin a single command and when using the default changelog generator.Updated dependencies [
2b49c39,74dda8c]:v2.17.0Compare Source
Minor Changes
bc611cfThanks @Andarist! - From now on, changeset files starting with a dot (e.g..ignored-temporarily.md) will be be ignored and kept around after versioning. This allows you to prepare a changeset for something that isn't supposed to be released immediately. An example use case could involve code hidden behind a feature flag.Patch Changes
#582
e89e28aThanks @Andarist! - Add support for publishConfig.registryUpdated dependencies [
bc611cf,e89e28a]:v2.16.0Compare Source
Minor Changes
#542
de2b4a5Thanks @Andarist! - A newupdateInternalDependentsexperimental option has been added. It can be used to add dependent packages to the release (if they are not already a part of it) with patch bumps. To use it you can add this to your config:{ "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": { "updateInternalDependents": "always" } }This option accepts two values -
"always"and"out-of-range"(the latter matches the current default behavior).#562
6353abfThanks @Andarist! - Stop asking for changeset confirmation when it has been provided using an external editor.Patch Changes
de2b4a5,de2b4a5]:v2.15.0Compare Source
Minor Changes
bb7106dThanks @Andarist! - Added new--openflag to theaddcommand. It opens the created changeset with an external editor.Patch Changes
8b9ac07]: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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.