From f87bb6e7f19c342cceef4c096be03b6646575197 Mon Sep 17 00:00:00 2001 From: Adam Stankiewicz Date: Wed, 9 Jun 2021 13:04:55 -0400 Subject: [PATCH] docs: update lerna publishing resolution how-to (#135) --- docs/how_tos/resolving_publishing_issues_with_lerna.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/how_tos/resolving_publishing_issues_with_lerna.rst b/docs/how_tos/resolving_publishing_issues_with_lerna.rst index 71cb9fb1..f48ec7e3 100644 --- a/docs/how_tos/resolving_publishing_issues_with_lerna.rst +++ b/docs/how_tos/resolving_publishing_issues_with_lerna.rst @@ -5,14 +5,14 @@ In setting up the Lerna monorepo, there was a moment when the ``lerna publish`` The result of this publishing failure was that the Git repository was in a state as if the release had been published, without the same, matching version existing on the NPM registry. This document serves as a starting point to resolve that situation. -In the scenario where Git tags and a "chore: publish" commit were created for a new release without that release actually being published to NPM, you may temporarily modify the ``release.yml`` Github Action workflow file to run the following command instead of the default ``lerna publish``: +In the scenario where Git tags and a "chore: publish" commit were created for a new release without that release actually being published to NPM, you may `temporarily modify the release.yml Github Action workflow file `_ to run the following command instead of the default ``lerna publish``: :: - lerna publish from-package --no-git-tag-version --no-push --yes + lerna publish from-package --yes By including the ``from-package`` option, Lerna will determine the package version to publish based on the existing version noted in the package.json files of each package in the monorepo. The ``--no-git-tag-version`` option tells Lerna to not attempt to create new Git tags for this release, because in this scenario, they were already created. The ``--no-push`` option tells Lerna to avoid creating a new "chore: publish" commit. See the `official Lerna documentation `_ for more details. -Be sure to remember reverting the ``release.yml`` back to its original state once the published NPM package(s) are back in a good state with matching and correct versions. +Be sure to remember to change the ``release.yml`` back to its original state once the published NPM package(s) are back in a good state with matching and correct versions.