@changesets/types

5.2.1

Patch Changes

#1033 521205d Thanks @Andarist! - Added changedFilePatterns property to Config and WrittenConfig types.

5.2.0

Minor Changes

#662 8c08469 Thanks @JakeGinnivan! - Added support for the privatePackages property in the config.

5.1.0

Minor Changes

#858 dd9b76f Thanks @dotansimha! - Added a new config option: snapshot.prereleaseTemplate for customizing the way snapshot release numbers are being composed.

5.0.0

Major Changes

#768 c87eba6 Thanks @rohit-gohri! - commit properties of config types were adjusted to account for this option potentially pointing to a module path.

4.1.0

Minor Changes

#690 27a5a82 Thanks @Andarist! - Add the new fixed property to the Config type.

4.0.2

Patch Changes

#668 9a993ba Thanks @marcodejongh! - Add resolutions to the PackageJSON type.

4.0.1

Patch Changes

#582 e89e28a Thanks @Andarist! - Add support for publishConfig.registry

4.0.0

Major Changes

#542 de2b4a5 Thanks @Andarist! - A new updateInternalDependents experimental option has been added. It can be used to add dependent packages to the release (if they are not already a part of it) with patch bumps. To use it you can add this to your config:
```
{
  "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
    "updateInternalDependents": "always"
  }
}
```
This option accepts two values - "always" and "out-of-range" (the latter matches the current default behavior).

3.3.0

Minor Changes

12f9a43 #507 Thanks @zkochan! - New setting added: bumpVersionsWithWorkspaceProtocolOnly. When it is set to true, versions are bumped in dependencies, only if those versions are prefixed by the workspace protocol. For instance, "foo": "workspace:^1.0.0".

3.2.0

Minor Changes

f4973a2 #467 Thanks @Andarist! - Exported a new Linked type for convenience - it's an alias for ReadonlyArray<ReadonlyArray<string>>.`

3.1.1

Patch Changes

a57d163 #428 Thanks @dotansimha! - Updated signature of PackageJSON['publishConfig'] to include directory?: string.

3.1.0

Minor Changes

9dcc364 #371 Thanks @Feiyang1! - Add ignore config option to configure ignored packages. The versions of ignored packages will not be bumped during a release, but their dependencies will still be bumped normally.

Patch Changes

addd725 #383 Thanks @Feiyang1! - Added an experimental flag onlyUpdatePeerDependentsWhenOutOfRange. When set to true, we only bump peer dependents when peerDependencies are leaving range.

3.0.0

Major Changes

2b49d66 #358 Thanks @Blasz! - Add new updateInternalDependencies config option to disable auto bumping of internal dependencies in the same release if the dependency was only patch bumped

2.0.1

Patch Changes

1706fb7 #321 Thanks @mitchellhamilton! - Fix TypeScript declarations

2.0.0

Major Changes

011d57f #313 Thanks @zkochan! - Add in none as a potential option for bumpType in release plans. Note that this is experimental and is internal, not a possible user option

1.0.1

Patch Changes

04ddfd7 #305 Thanks @Noviny! - Add link to changelog in readme
e56928b #298 Thanks @eps1lon! - In changelog-github, throw more descriptive error when no options are provided.

1.0.0

Major Changes

cc8c921 #290 Thanks @mitchellhamilton! - Rename ModCompWithWorkspace to ModCompWithPackage and change config key with packageJson
cc8c921 #290 Thanks @mitchellhamilton! - Remove Workspace type. You should use the Package type from @manypkg/get-packages instead.

Minor Changes

41e2e3d #292 Thanks @acheronfail! - Add new Changeset type

Patch Changes

2363366 #291 Thanks @acheronfail! - Add baseBranch to Config type

0.4.0

Minor Changes

8f0a1ef #183 Thanks @mitchellhamilton! - Add PreState type and preState property to ReleasePlan

0.3.1

Patch Changes

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.

0.3.0

Minor Changes

1ff73b7 #156 Thanks @mitchellhamilton! - Remove Changeset type because it isn't used and make commit optional on NewChangesetWithCommit because the commit won't always exist

Patch Changes

8c43fa0 #155 Thanks @Noviny! - Add Readme

0.2.0

Minor Changes

296a6731 - Safety bump: Towards the end of preparing changesets v2, there was a lot of chaos - this bump is to ensure every package on npm matches what is found in the repository.

0.1.2

Patch Changes

a15abbf9 - Previous release shipped unbuilt code - fixing that

0.1.0

Minor Changes

6d119893 - Initial Release
519b4218 - Add WrittenConfig type and include all properties in Config type