@changesets/cli

Minor Changes

• a679b1d #204 Thanks @Andarist! - Respect publishConfig.access in workspace package.jsons

  Previously, every package in your repository had one 'public' or 'restricted' setting.

  Now, if a workspace has publishConfig.access in its package.json, we will prioritize it over the global changesets config.

• 51a0d76 #182 Thanks @ajaymathur! - Updated the package to use the new @changesets/logger for logging.

Patch Changes

• 5ababa0 #201 Thanks @ajaymathur! - Updated to use the Error classes from the @changesets/errors package

• a679b1d #204 Thanks @Andarist! - Correctly handle the 'access' flag for packages

  Previously, we had access as "public" or "private", access "private" isn't valid. This was a confusing because there are three states for publishing a package:

  • private: true - the package will not be published to npm (worked)
  • access: public - the package will be publicly published to npm (even if it uses a scope) (worked)
  • access: restricted - the package will be published to npm, but only visible/accessible by those who are part of the scope. This technically worked, but we were passing the wrong bit of information in.

  Now, we pass the correct access options public or restricted.