`linked` config setting not working as expected?

Affected Packages

pkg:cli

Problem

I was assuming linked would help with enforcing packages to always use the same version amongst each other, similar to how Lerna does. However that appears to not be the case. Here’s the recent versioning pull request on Slate that shows the issue: https://github.com/ianstormtaylor/slate/pull/4198

Both slate and slate-react are bumped to 0.62.1 but the others are left at 0.62.0.

Proposed solution

Either change linked to keep things at the same version, or potentially add another setting called pinned or something that does it. The use case being keeping a set of packages always on the same version when one of them is bumped so that people can be guaranteed to have packages that work together really easily. (I believe this is what popular projects like Babel and React do?)

[glasser]

Agreed that this would be useful — changesets looks awesome and I’d love to migrate Apollo Server from lerna to it, but we depend on being able to publish all of our “entry point” packages (apollo-server-express, apollo-server-lambda, etc) at the same version so we can talk about v3.1.2 of Apollo Server in a simple way.

[glasser]

Very cool, though my project might just manage to migrate to a single-package release instead of a monorepo 😃