Skip to content

versioning-apps.md

Latest commit

 

History

History
36 lines (24 loc) · 1.52 KB

versioning-apps.md

File metadata and controls

36 lines (24 loc) · 1.52 KB

Managing applications or non-npm packages

Changesets can also be used to manage application versions or non-npm packages (ie dotnet NuGet packages, ruby gems, docker images etc).

The only requirement is that the project has a package.json file to manage the versions and dependencies within the repo.

To enable this feature set privatePackages to { version: true, tag: true } in your .changesets/config.json file. By default changesets will only update the changelog and version (ie { version: true, tag: false }).

Note Changesets only versions NPM package.json files, you can trigger releases for other package formats by creating workflows which trigger on tags/releases being created by changesets.

Setting up a package

To enable a project to be tracked by changesets, it needs a minimal package.json with at least name, private and version.

{
  "name": "my-project",
  "private": true,
  "version": "0.0.1"
}

Private dependencies

When a versioned private package (app) depends on another private package that is skipped (either via the ignore option or privatePackages.version: false), changesets will not require the app to also be skipped. Since private packages are not published to npm, it is safe for them to depend on skipped packages.

For example, if you have an app A that depends on a private library B, you can ignore B while still versioning A:

{
  "ignore": ["B"]
}

This works because A is private and will never be published to npm with a stale reference to B.