- #854
2827c7a
Thanks @Andarist! - Fixed the declared JSON schema type for thechangelog
config option.
- #852
7b1c0c1
Thanks @caohuilin! - Fixed the declared JSON schema type for thecommit
config option.
- #768
c87eba6
Thanks @rohit-gohri! - The parsed config now normalzied the commit option to eitherfalse
or a tuple describing what module should be loaded to resolve commit functions.
- Updated dependencies [
c87eba6
]:- @changesets/types@5.0.0
- @changesets/get-dependents-graph@1.3.2
- #690
27a5a82
Thanks @Andarist! - Added parsing and validating of the newfixed
option. The description for this option has also been added to the JSON schema.
- Updated dependencies [
27a5a82
]:- @changesets/types@4.1.0
- @changesets/get-dependents-graph@1.3.1
- Updated dependencies [
6f9c9d6
]:- @changesets/get-dependents-graph@1.3.0
-
#667
fe8db75
Thanks @fz6m! - Upgraded@manypkg/get-packages
dependency to fix getting correct packages in pnpm workspaces with exclude rules. -
Updated dependencies [
fe8db75
,9a993ba
]:- @changesets/get-dependents-graph@1.2.4
- @changesets/types@4.0.2
- Updated dependencies [
74dda8c
]:- @changesets/get-dependents-graph@1.2.3
- Updated dependencies [
e89e28a
]:- @changesets/types@4.0.1
- @changesets/get-dependents-graph@1.2.2
-
#542
de2b4a5
Thanks @Andarist! - A newupdateInternalDependents
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).
- Updated dependencies [
de2b4a5
]:- @changesets/types@4.0.0
- @changesets/get-dependents-graph@1.2.1
12f9a43
#507 Thanks @zkochan! - New setting added: bumpVersionsWithWorkspaceProtocolOnly. When it is set totrue
, versions are bumped independencies
, only if those versions are prefixed by the workspace protocol. For instance,"foo": "workspace:^1.0.0"
.
- Updated dependencies [
12f9a43
]:- @changesets/get-dependents-graph@1.2.0
- @changesets/types@3.3.0
e33e4ca
#458 Thanks @emmenko! - Allow glob expressions to be provided for thelinked
andignore
options
- Updated dependencies [
f4973a2
]:- @changesets/types@3.2.0
377f5c3
#393 Thanks @Andarist! - AddedupdateInternalDependencies
andignore
options to the JSON schema.
377f5c3
#393 Thanks @Andarist! - Removed experimental flags fromdefaultWrittenConfig
. They were added there by mistake.
9dcc364
#371 Thanks @Feiyang1! - Addignore
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.
-
addd725
#383 Thanks @Feiyang1! - Added an experimental flagonlyUpdatePeerDependentsWhenOutOfRange
. When set totrue
, we only bump peer dependents when peerDependencies are leaving range. -
Updated dependencies [
addd725
,9dcc364
]:- @changesets/types@3.1.0
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
- Updated dependencies [
2b49d66
]:- @changesets/types@3.0.0
-
1706fb7
#321 Thanks @mitchellhamilton! - Fix TypeScript declarations -
Updated dependencies [
1706fb7
]:- @changesets/errors@0.1.4
- @changesets/logger@0.0.5
- @changesets/types@2.0.1
- Updated dependencies [
011d57f
]:- @changesets/types@2.0.0
-
b49e1cf
#306 Thanks @Andarist! - Ignorenode_modules
when glob searching for packages. This fixes an issue with package cycles. -
Updated dependencies [
04ddfd7
,e56928b
]:- @changesets/errors@0.1.3
- @changesets/logger@0.0.4
- @changesets/types@1.0.1
cc8c921
#290 Thanks @mitchellhamilton! - AcceptPackages
object from@manypkg/get-workspaces
instead ofWorkspace[]
fromget-workspaces
bca8865
#221 Thanks @mitchellhamilton! - Added support forbaseBranch
option which specifies what branch Changesets should use when determining what packages have changed
- Updated dependencies [
9cd1eaf
]:- @changesets/logger@0.0.3
- Updated dependencies [
8f0a1ef
,8f0a1ef
,8f0a1ef
]:- @changesets/types@0.4.0
- @changesets/errors@0.1.2
- @changesets/logger@0.0.2
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 packagesPreviously, 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
orrestricted
. -
Updated dependencies [
51a0d76
,a679b1d
,5ababa0
]:- @changesets/logger@0.0.1
- @changesets/types@0.3.1
- @changesets/errors@0.1.1
- Updated dependencies [8c43fa0, 1ff73b7]:
- @changesets/types@0.3.0
- 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.
- Updated dependencies [296a6731]:
- @changesets/types@0.2.0
- a15abbf9 - Previous release shipped unbuilt code - fixing that
-
519b4218 - Initial release with parse and read functions along with defaultConfig and defaultWrittenConfig
-
Updated dependencies [519b4218]:
- @changesets/types@0.1.0