@changesets/cli 2.18.0 release notes

2.18.0

#634 2b49c39 Thanks @joeldenning! - The new changeset tag command 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 publish is executed, running changeset tag is not needed.

Note that it is expected that changeset version is run before changeset tag, so that the package.json versions 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 respective package.json.

#585 74dda8c Thanks @javier-garcia-meteologica! - Add support for workspace:^ and workspace:~ dependency ranges.
#660 5413f3e Thanks @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 running changeset add && changeset version in a single command and when using the default changelog generator.
Updated dependencies [2b49c39, 74dda8c]:
- @changesets/git@1.2.0
- @changesets/apply-release-plan@5.0.2

#634 2b49c39 Thanks @joeldenning! - The new changeset tag command 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 publish is executed, running changeset tag is not needed.

Note that it is expected that changeset version is run before changeset tag, so that the package.json versions 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 respective package.json.

#585 74dda8c Thanks @javier-garcia-meteologica! - Add support for workspace:^ and workspace:~ dependency ranges.
#660 5413f3e Thanks @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 running changeset add && changeset version in a single command and when using the default changelog generator.
Updated dependencies [2b49c39, 74dda8c]:
- @changesets/git@1.2.0
- @changesets/apply-release-plan@5.0.2