From 47016fc6cb43a8dad6c155b7a1191c8f5613d7aa Mon Sep 17 00:00:00 2001 From: Matic Zavadlal Date: Sun, 2 Jul 2023 23:07:47 +0200 Subject: [PATCH] add pnpm docs to publish command (#1181) --- docs/command-line-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/command-line-options.md b/docs/command-line-options.md index b827a1c90..109720c12 100644 --- a/docs/command-line-options.md +++ b/docs/command-line-options.md @@ -101,7 +101,7 @@ Snapshot is used for a special kind of publishing for testing - it creates tempo changeset publish [--otp={token}] ``` -This publishes changes to npm, and creates git tags. This works by going into each package, checking if the version it has in its `package.json` is published on npm, and if it is not, running the `npm publish`. +This publishes changes to npm, and creates git tags. This works by going into each package, checking if the version it has in its `package.json` is published on npm, and if it is not, running the `npm publish`. If you are using `pnpm` as a package manager, this automatically detects it and uses `pnpm publish` instead. Because this command assumes that the last commit is the release commit, you should not commit any changes between calling version and publish. These commands are separate to enable you to check if the release changes are accurate.