Release @changesets/cli@2.25.0 · changesets/changesets

#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.

#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

Provide feedback