bump-workspaces

Scenario I have two packages in the workspace: and . depends on (i.e. depends on ). Then, I make a breaking change in and run this CLI. Actual result It makes a minor release of . That's fine. Expected result It should also make a minor release of , which would be dependent on . Otherwise there is still that relies on , which isn't compatible with . Therefore, there is no chance to get of version that depends on , though technically it exists and must be published. This would be consistent e.g. with - How dependencies are bumped: For example, if I have two packages: at and at that depends on at . If I add to a changeset with a change, the version of within the mono-repo should also be updated. If it is not, either in the mono-repo will not use in development, or in development will not match an installation of in production. As such we end up with a changeset that includes as and as . All updating of dependencies is done as a patch bump. If you want to indicate a more significant change to from consuming a new version of , we recommend adding a second changeset specifically for .