Skip to content

Latest commit

History

History
175 lines (96 loc) 路 7.27 KB

CHANGELOG.md

File metadata and controls

175 lines (96 loc) 路 7.27 KB

get-workspaces

1.0.9

Patch Changes

  • Updated dependencies [8c08469]:
    • @changesets/types@5.2.0

1.0.8

Patch Changes

  • Updated dependencies [dd9b76f]:
    • @changesets/types@5.1.0

1.0.7

Patch Changes

  • Updated dependencies [c87eba6]:
    • @changesets/types@5.0.0

1.0.6

Patch Changes

  • Updated dependencies [27a5a82]:
    • @changesets/types@4.1.0

1.0.5

Patch Changes

  • Updated dependencies [9a993ba]:
    • @changesets/types@4.0.2

1.0.4

Patch Changes

  • Updated dependencies [e89e28a]:
    • @changesets/types@4.0.1

1.0.3

Patch Changes

  • Updated dependencies [de2b4a5]:
    • @changesets/types@4.0.0

1.0.2

Patch Changes

  • Updated dependencies [2b49d66]:
    • @changesets/types@3.0.0

1.0.1

Patch Changes

  • Updated dependencies [011d57f]:
    • @changesets/types@2.0.0

1.0.0

Major Changes

  • cc8c921 #290 Thanks @mitchellhamilton! - get-workspaces has been replaced by @manypkg/get-packages, please use that package instead. See @manypkg/get-packages README for the API changes.

Patch Changes

0.6.0

Minor Changes

  • fe0d9192 #236 Thanks @Andarist! - Added support for finding pnpm workspace packages. It has been added to default queried tools.

  • fe0d9192 #236 Thanks @Andarist! - Read also pnpm workspace packages when searching for packages.

0.5.2

Patch Changes

  • Updated dependencies [8f0a1ef]:
    • @changesets/types@0.4.0

0.5.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.

  • Updated dependencies [a679b1d]:

    • @changesets/types@0.3.1

0.5.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.4.2

Patch Changes

  • a15abbf9 - Previous release shipped unbuilt code - fixing that

0.4.0

Minor Changes

Patch Changes

0.3.1

Patch Changes

  • 20da7747 #66 Thanks @Noviny! - Update package.json field so each links into its own package

0.3.0

Minor Changes

Patch Changes

  • a966701d - Add repository information to package.json

0.2.1

Patch Changes

  • 67db935d - Fix release without built files

0.2.0

Minor Changes

Patch Changes

0.1.1

Patch Changes

  • bed96aa2 #35 Thanks @mitchellhamilton! - Use workspaces.packages instead of the incorrect workspaces.package field for resolving yarn workspaces

0.1.0

Minor Changes

  • b93d04a2 - Initial release of get-workspaces