A tool to manage versioning and changelogs with a focus on monorepos
Published Node.js and peer-dependency requirements.
Neither version declares Node.js or peer-dependency requirements.
31 Oct 2019 · Newest first
Last checked
Checking sources…
Showing 1 of 1 releases. Full release notes.
Signals highlight changes worth reviewing. They cannot determine whether your application is affected.
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.
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.
da11ab8 #205 Thanks @mitchellhamilton! - Don't update ranges set to */x/X when versioning
Updated dependencies [51a0d76, 5ababa0, a679b1d, 5ababa0, da11ab8]: