From f53af5375c700a5f6dfb36afca704af1b106dad6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mateusz=20Burzy=C5=84ski?= Date: Thu, 9 Dec 2021 16:08:36 +0100 Subject: [PATCH] Fix Changesets references in the docs --- docs/pages/docs/guides/complimentary-tools.mdx | 4 ++-- docs/pages/docs/guides/migrate-from-lerna.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/pages/docs/guides/complimentary-tools.mdx b/docs/pages/docs/guides/complimentary-tools.mdx index b212c2eca1a04..0220846b8d089 100644 --- a/docs/pages/docs/guides/complimentary-tools.mdx +++ b/docs/pages/docs/guides/complimentary-tools.mdx @@ -10,9 +10,9 @@ Below is a running list of additional monorepo tools that you may find useful in ## Versioning, Publishing, and Changelog Generation -For the foreseable future, `turbo` is not going to deal with package publishing. Versioning/Publishing is an extremely opinionated topic with a lot of existing solutions. Our advice is to avoid versioning packages altogether unless you actually need to publish them to NPM for external consumption. If you have to version your packages, we really like the workflow of changesets (especially for open source projects). +For the foreseable future, `turbo` is not going to deal with package publishing. Versioning/Publishing is an extremely opinionated topic with a lot of existing solutions. Our advice is to avoid versioning packages altogether unless you actually need to publish them to NPM for external consumption. If you have to version your packages, we really like the workflow of Changesets (especially for open source projects). -- [atlassian/changesets](https://github.com/atlassian/changesets) - 🦋 A way to manage your versioning and changelogs with a focus on monorepos +- [changesets/changesets](https://github.com/changesets/changesets) - 🦋 A way to manage your versioning and changelogs with a focus on monorepos - [microsoft/beachball](https://github.com/microsoft/beachball) - The Sunniest Semantic Version Bumper - [lerna/lerna](https://github.com/lerna/lerna) - A tool for managing JavaScript projects with multiple packages. - [lerna/lerna-changelog](https://github.com/lerna/lerna-changelog) - PR-based changelog generator with monorepo support diff --git a/docs/pages/docs/guides/migrate-from-lerna.mdx b/docs/pages/docs/guides/migrate-from-lerna.mdx index 5c727b1ae87fe..ff49f804eb752 100644 --- a/docs/pages/docs/guides/migrate-from-lerna.mdx +++ b/docs/pages/docs/guides/migrate-from-lerna.mdx @@ -27,7 +27,7 @@ The above may not not look like much. But imagine that A's `build` task takes 20 ### Package Publishing, Versioning, and Changelog Generation -Lerna can version and publish packages to NPM registries as well as create changelogs. It's extremely good at this, especially for releasing canary pre-releases. While Turborepo may eventually tackle these features, at the time of writing, it is not a high priority goal (we suggest using using [atlassian/changesets](https://github.com/atlassian/changesets) in the meantime). If changesets isn't for you, and you want to stick with Lerna's publish flow, you can use Lerna and Turborepo together. +Lerna can version and publish packages to NPM registries as well as create changelogs. It's extremely good at this, especially for releasing canary pre-releases. While Turborepo may eventually tackle these features, at the time of writing, it is not a high priority goal (we suggest using using [Changesets](https://github.com/changesets/changesets) in the meantime). If Changesets isn't for you, and you want to stick with Lerna's publish flow, you can use Lerna and Turborepo together. ## Example migration