-
Notifications
You must be signed in to change notification settings - Fork 1
Update dependency @changesets/cli to v2.27.1 #46
base: master
Are you sure you want to change the base?
Conversation
|
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
0dd2597
to
7e70e6f
Compare
7e70e6f
to
b06bdad
Compare
b06bdad
to
4e26976
Compare
4e26976
to
845ec03
Compare
845ec03
to
629d103
Compare
629d103
to
7a0ed7f
Compare
7a0ed7f
to
6d717c9
Compare
6d717c9
to
4faab9a
Compare
⚠ Artifact update problemRenovate failed to update an artifact 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:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
4faab9a
to
074d241
Compare
This PR contains the following updates:
2.19.0
->2.27.1
Release Notes
changesets/changesets (@changesets/cli)
v2.27.1
Compare Source
Patch Changes
86cfff1
Thanks @Andarist! - Make./bin.js
available throughpackage.json#exports
to fix compatibility withchangesets/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 IDsPatch Changes
#1053
90a870a
Thanks @paescuj! - Replace the dependencyis-ci
withci-info
.Updated dependencies [
a971652
,dfd4cca
]:v2.26.2
Compare Source
Patch Changes
#1176
41988ce
Thanks @joshwooding! - Bumpsemver
dependency to v7.5.3Updated dependencies [
41988ce
]:v2.26.1
Compare Source
Patch Changes
feddc88
Thanks @Andarist! - Callpnpm publish
directly from the directory of the published package. This allowspnpm
to correctly handle configuredpublishConfig.directory
.v2.26.0
Compare Source
Minor Changes
#1033
521205d
Thanks @Andarist! - A new config-levelchangedFilePatterns
option 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 add
andchangeset status
.Patch Changes
598136a
,521205d
,521205d
,598136a
,598136a
,521205d
]:v2.25.2
Compare Source
Patch Changes
6cc4300
]: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 theprivatePackages.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 invokingchangeset 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:With a changeset for
pkg-a
thepkg-c
could have been sometimes incorrectly released.Updated dependencies [
8c08469
,8c08469
,64585ea
]:v2.24.4
Compare Source
Patch Changes
c140171
]:v2.24.3
Compare Source
Patch Changes
b023e4b
]:v2.24.2
Compare Source
Patch Changes
#900
7d998ee
Thanks @sdirosa! - Fixed an issue with generating changelogs not being skipped when thechangelog
config option was set tofalse
.#720
0fd56e1
Thanks @bhovhannes! - Private packages without aversion
field are no longer listed when adding a changeset.#844
8627ec1
Thanks @Andarist! - Attempt to logstdout
when publish fails ifstderr
is empty and JSON error can't be retrieved from none of those.Updated dependencies [
7d998ee
,7d998ee
]:v2.24.1
Compare Source
Patch Changes
f64bc1b
]:v2.24.0
Compare Source
Minor Changes
#858
dd9b76f
Thanks @dotansimha! - Added a new config flag forchangesets 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 calledsnapshot
.To migrate, make sure to update your
config.json
.Old usage (still works, but comes with a deprecated warning):
New usage:
Updated dependencies [
dd9b76f
,dd9b76f
,dd9b76f
]:v2.23.2
Compare Source
Patch Changes
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 ofchangeset 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
]:v2.23.0
Compare Source
Minor Changes
745b771
Thanks @JakeGinnivan! - Upgradedtty-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
]:v2.22.0
Compare Source
Minor Changes
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 containgetAddMessage
and/orgetVersionMessage
. 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 configurebaseBranch: "main"
in the.changeset/config.json
as the default value.#770
eb86652
Thanks @alizeait! -changeset add
andchangeset 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
]:v2.21.1
Compare Source
Patch Changes
#760
5a2a59a
Thanks @Andarist! - Fixed an issue with logging non-stringified Buffers in case of publish errors.#769
3e8e672
Thanks @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.0
Compare Source
Minor Changes
#690
27a5a82
Thanks @Andarist! - Added a new.changeset/config.json
option: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
0812858
Thanks @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
15c461d
Thanks @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
d14cf79
Thanks @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 version
for the very first time for a package).#751
59c7ebc
Thanks @Rugvip! - Fixed an issue where dependent packages would sometimes not get bumped properly when exiting prerelease mode.#703
15c461d
Thanks @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.0
Compare Source
Minor Changes
#698
9e14a9a
Thanks @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
6f9c9d6
Thanks @Andarist! - Dependencies specified using a tag will no longer result in printing incorrect errors in the console.Patch Changes
#740
957e39c
Thanks @akphi! - Fixed an issue with failing to parse changesets containing a completely empty summary.#693
1be201f
Thanks @luciaquirke! - Fixed an issue withnone
release type sometimes overriding other release types and thus preventing a release from happening.Updated dependencies [
6f9c9d6
,77c1cef
,1be201f
]: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.
This PR has been generated by Mend Renovate. View repository job log here.