Changesets

Appearance

Linked Packages ​

Linked packages allow you to specify a group or groups of packages that should be versioned together. They can be configured with the linked option. There are some complex cases, so some examples are shown below to demonstrate various cases.

  • Linked packages will only be bumped when there is a changeset for them. This can mean because you explicitly choose to add a changeset for it or because it's a dependent of something being released.
  • Packages that have changesets and are in a set of linked packages will always be versioned based on the highest current version in the set of linked packages and the highest bump type from changesets in the set of linked packages.

Compared to fixed packages

With linked packages, there is no guarantee that all packages in the group will be version-bumped and published, only those with changesets will be.

Examples ​

General Example ​

We have three packages, pkg-a, pkg-b, and pkg-c. pkg-a and pkg-b are linked, but pkg-c is not so the config looks like this:

.changeset/config.json
json
{
  "linked": [["pkg-a", "pkg-b"]]
}
  • pkg-a is at 1.0.0
  • pkg-b is at 1.0.0
  • pkg-c is at 1.0.0

We have a changeset with a patch for pkg-a, minor for pkg-b and major for pkg-c, and we do a release, the resulting versions will be:

  • pkg-a is at 1.1.0
  • pkg-b is at 1.1.0
  • pkg-c is at 2.0.0

We now have another changeset with a minor for pkg-a, and we do a release, the resulting versions will be:

  • pkg-a is at 1.2.0
  • pkg-b is at 1.1.0
  • pkg-c is at 2.0.0

We now have another changeset with a minor for pkg-b, and we do a release, the resulting versions will be:

  • pkg-a is at 1.2.0
  • pkg-b is at 1.3.0
  • pkg-c is at 2.0.0

We now have another changeset with patches for all three packages, and we do a release, the resulting versions will be:

  • pkg-a is at 1.3.1
  • pkg-b is at 1.3.1
  • pkg-c is at 2.0.1

With dependencies ​

We have two packages, pkg-a and pkg-b which are linked. pkg-a has a dependency on pkg-b.

.changeset/config.json
json
{
  "linked": [["pkg-a", "pkg-b"]]
}
  • pkg-a is at 1.0.0
  • pkg-b is at 1.0.0

We have a changeset with a major for pkg-b, and we do a release, the resulting versions will be:

  • pkg-a is at 2.0.0
  • pkg-b is at 2.0.0

We now have another changeset with a major for pkg-a, and we do a release, the resulting versions will be:

  • pkg-a is at 3.0.0
  • pkg-b is at 2.0.0