From 60d4cceb4fb021b82fec2ef45a6d530fe9f3ddad Mon Sep 17 00:00:00 2001 From: Greg Hurrell Date: Fri, 2 Oct 2020 12:26:24 +0200 Subject: [PATCH] docs(npm-tools): update a stale link This one was still pointing at the old repo (which is now archived/read-only) instead of the monorepo. --- projects/npm-tools/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/npm-tools/CONTRIBUTING.md b/projects/npm-tools/CONTRIBUTING.md index e117326793..8b018c20e1 100644 --- a/projects/npm-tools/CONTRIBUTING.md +++ b/projects/npm-tools/CONTRIBUTING.md @@ -42,7 +42,7 @@ Running `yarn version` has the following effects: - A tagged commit is created, including the changes to the changelog that you previously staged. - The "postversion" script will run, which automatically does `git push` and performs a `yarn publish`, prompting for confirmation along the way. -Copy the relevant section from the changelog to the corresponding entry on the [releases page](https://github.com/liferay/liferay-npm-tools/releases). +Copy the relevant section from the changelog to the corresponding entry on the [releases page](https://github.com/liferay/liferay-frontend-projects/releases). After the release, you can confirm that the packages are correctly listed in the NPM registry: