-
#857
7febb59
Thanks @dotansimha! - Fixed an issue with dependency ranges still using pre-existing range modifiers instead of fixed package versions when performing a snapshot release. This ensures that installs of snapshot versions are always reproducible. -
Updated dependencies [
2827c7a
,7b1c0c1
]:- @changesets/config@2.0.1
- #768
c87eba6
Thanks @rohit-gohri! - This module is no longer responsible for commiting files - this responsibility has been moved entirely to@changesets/cli
.
- Updated dependencies [
c87eba6
,eb86652
,c87eba6
]:- @changesets/types@5.0.0
- @changesets/git@1.3.2
- @changesets/config@2.0.0
- #703
15c461d
Thanks @Andarist! - Fixed an issue with*
dependency ranges not being replaced in premode. Those have to replaced with exact versions because prereleases don't satisfy wildcard ranges. A published prerelease package with such dependency range left untouched won't install correct prerelease dependency version.
-
#749
d14cf79
Thanks @Andarist! - Fixed an issue that caused created CHANGELOG files not being formatted in the same way as the updated ones (this could happen when callingchangeset version
for the very first time for a package). -
Updated dependencies [
27a5a82
,27a5a82
]:- @changesets/types@4.1.0
- @changesets/config@1.7.0
- @changesets/git@1.3.1
- Updated dependencies [
77c1cef
]:- @changesets/git@1.3.0
- @changesets/config@1.6.4
-
#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/config@1.6.3
- @changesets/git@1.2.1
- @changesets/types@4.0.2
-
#585
74dda8c
Thanks @javier-garcia-meteologica! - Add support forworkspace:^
andworkspace:~
dependency ranges. -
Updated dependencies [
2b49c39
]:- @changesets/git@1.2.0
- @changesets/config@1.6.2
- Updated dependencies [
e89e28a
]:- @changesets/types@4.0.1
- @changesets/config@1.6.1
- @changesets/git@1.1.2
- #542
de2b4a5
Thanks @Andarist! - The acceptedConfig
type has been changed - a new experimental option (updateInternalDependents
) was added to it.
- Updated dependencies [
de2b4a5
]:- @changesets/config@1.6.0
- @changesets/types@4.0.0
- @changesets/git@1.1.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/config@1.5.0
- @changesets/types@3.3.0
fd53ca2
#395 Thanks @jonathanmorley! - UseJSON.stringify
to update package.jsons without including modifications from prettier.
addd725
#383 Thanks @Feiyang1! - Added an experimental flagonlyUpdatePeerDependentsWhenOutOfRange
. When set totrue
, we only bump peer dependents when peerDependencies are leaving range.
-
9dcc364
#371 Thanks @Feiyang1! - Added support for ignoring packages in theversion
command. The version of ignored packages will not be bumped, but their dependencies will still be bumped normally. This is useful when you have private packages, e.g. packages under development. It allows you to make releases for the public packages without changing the version of your private packages. To use the feature, you can define theignore
array in the config file with the name of the packages:{ ... "ignore": ["pkg-a", "pkg-b"] ... }
or you can pass the package names to the
--ignore
flag when using cli:yarn changeset version --ignore pkg-a --ignore --pkg-b
-
6d0790a
#359 Thanks @ajaymathur! - Add support for snapshot flag to version command. Usage:changeset version --snapshot [tag]
. The updated version of the packages looks like0.0.0[-tag]-YYYYMMDDHHMMSS
where YYYY, MM, DD, HH, MM, and SS is the date and time of when the snapshot version is created. You can use this feature with the tag option in the publish command to publish packages under experimental tags from feature branches. To publish a snapshot version of a package under an experimental tag you can do:# Version packages to snapshot version changeset version --snapshot # Publish packages under experimental tag, keeping next and latest tag clean changeset publish --tag experimental
90f3b65
#373 Thanks @Blasz! - Fix patch bumped dependencies not being updated in dependents package.json when leaving semver range withupdateInternalDependencies
set to minor.
8fe77b6
#366 Thanks @Blasz! - Fix release version commit including dev dependent packages with release type 'none'
52a88ce
#361 Thanks @Blasz! - Fix dependency release lines being output when they were skipped via the updateInternalDependencies config option
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 [
89f0c49
,2b49d66
,09f62f9
]:- @changesets/git@1.0.5
- @changesets/types@3.0.0
- @changesets/config@1.1.0
3dbab2e
#343 Thanks @zkochan! - Self-references should be skipped when bumping versions. A self-reference is a dev dep that has the same name as the package. Some projects use self-references as a convenient way to require files using relative paths from the root directory.
-
1706fb7
#321 Thanks @mitchellhamilton! - Fix TypeScript declarations -
Updated dependencies [
1706fb7
]:- @changesets/config@1.0.3
- @changesets/get-version-range-type@0.3.2
- @changesets/git@1.0.3
- @changesets/types@2.0.1
-
011d57f
#313 Thanks @zkochan! - BumpingdevDependencies
no longer bumps the packages that they depend on.This is a pretty big "quality of life" update, which means we will do fewer releases of packages overall, as there is no change of installed packages.
This has been made a breaking change as it changes the behavior of what will be published. It should only be for the better, but we didn't want to surprise you with it.
-
011d57f
#313 Thanks @zkochan! - Updates to devDependencies are not affecting the end users of a package. So we are not listing these changes in the changelog file.
c3cc232
#311 Thanks @zkochan! - Added support for workspace ranges. They are now correctly kept and updated when applying a release plan.
-
44555b4
#315 Thanks @maraisr! - Allows prettier to know about filepaths so it can apply file overrides -
Updated dependencies [
011d57f
]:- @changesets/types@2.0.0
- @changesets/config@1.0.2
- @changesets/git@1.0.2
-
04ddfd7
#305 Thanks @Noviny! - Add link to changelog in readme -
b49e1cf
#306 Thanks @Andarist! - Ignorenode_modules
when glob searching for packages. This fixes an issue with package cycles. -
Updated dependencies [
04ddfd7
,e56928b
,b49e1cf
]:- @changesets/config@1.0.1
- @changesets/get-version-range-type@0.3.1
- @changesets/git@1.0.1
- @changesets/types@1.0.1
cc8c921
#290 Thanks @mitchellhamilton! - AcceptPackages
object from@manypkg/get-packages
instead ofcwd
- Updated dependencies [
41e2e3d
,cc8c921
,cc8c921
,cc8c921
,2363366
,cc8c921
]:- @changesets/types@1.0.0
- @changesets/git@1.0.0
- @changesets/config@1.0.0
- Updated dependencies [
d08c3b3
]:- @changesets/get-version-range-type@0.3.0
- Updated dependencies [
1282ef6
]:- @changesets/get-version-range-type@0.2.0
-
ef6402c9
#252 Thanks @Andarist! - Ensure there is a newline between release lines so the final markdown preserves correct formatting. -
503154db
#257 Thanks @Noviny! - Move catch statement so errors are less spammy -
Updated dependencies [
fe0d9192
,fe0d9192
]:- get-workspaces@0.6.0
- @changesets/git@0.4.0
8f0a1ef
#183 Thanks @mitchellhamilton! - Add support for prereleases. For more information, see the docs on prereleases.
- Updated dependencies [
8f0a1ef
]:- @changesets/types@0.4.0
- @changesets/config@0.2.3
- get-workspaces@0.5.2
- @changesets/git@0.2.4
-
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
. -
da11ab8
#205 Thanks @mitchellhamilton! - Don't update ranges set to */x/X when versioning -
Updated dependencies [
5ababa0
,a679b1d
]:- @changesets/config@0.2.2
- get-workspaces@0.5.1
- @changesets/types@0.3.1
-
72babcb
#178 Thanks @mitchellhamilton! - Fix changelog generator options not being provided -
Updated dependencies []:
- @changesets/git@0.2.3
-
1ff73b7 #156 Thanks @mitchellhamilton! - Fix commits not being obtained for old changesets
-
0320391 #163 Thanks @Noviny! - Reordered dependencies in the package json (this should have no impact)
-
Updated dependencies [8c43fa0, 0320391, 1ff73b7]:
- @changesets/get-version-range-type@0.1.1
- @changesets/git@0.2.1
- @changesets/types@0.3.0
- @changesets/config@0.2.1
- 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/config@0.2.0
- @changesets/get-version-range-type@0.1.0
- get-workspaces@0.5.0
- @changesets/git@0.2.0
- @changesets/types@0.2.0
- a15abbf9 - Previous release shipped unbuilt code - fixing that
- fded7cce - Initial release