chore(deps): update dependency @changesets/cli to ^2.25.0
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @changesets/cli | ^2.23.2 -> ^2.25.0 |
Release Notes
changesets/changesets
v2.25.0
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:pkg-a - version: 1.0.0 pkg-b - devDependencies['pkg-a']: 1.0.0 pkg-c - dependencies['pkg-b']: 1.0.0With a changeset for
pkg-athepkg-ccould 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
Patch Changes
- Updated dependencies [
c140171]:
v2.24.3
Patch Changes
- Updated dependencies [
b023e4b]:
v2.24.2
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.
v2.24.1
Patch Changes
- Updated dependencies [
f64bc1b]:
v2.24.0
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]:- @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
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone America/Vancouver, 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, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
⚠️ No Changeset found
Latest commit: df5eaf42a21ea8a11fbbef036f1c12cf185858c0
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