From b4b966879e7ae74d92826a485d87838bd0da1d90 Mon Sep 17 00:00:00 2001 From: Mark Stacey Date: Tue, 8 Nov 2022 20:49:29 -0330 Subject: [PATCH] Update publishing instructions The publishing instructions in the README have been updated to reflect changes introduced in #44. We forgot to update the README in that PR. The release instructions should now match those in the module template. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index ede8691..fa31d67 100644 --- a/README.md +++ b/README.md @@ -72,6 +72,6 @@ The project follows the same release process as the other libraries in the MetaM 7. Publish the release on npm. - - Be very careful to use a clean local environment to publish the release, and follow exactly the same steps used during CI. - - Use `npm publish --dry-run` to examine the release contents to ensure the correct files are included. Compare to previous releases if necessary (e.g. using `https://unpkg.com/browse/[package name]@[package version]/`). - - Once you are confident the release contents are correct, publish the release using `npm publish`. + - Wait for the `publish-release` GitHub Action workflow to finish. This should trigger a second job (`publish-npm`), which will wait for a run approval by the [`npm publishers`](https://github.com/orgs/MetaMask/teams/npm-publishers) team. + - Approve the `publish-npm` job (or ask somebody on the npm publishers team to approve it for you). + - Once the `publish-npm` job has finished, check npm to verify that it has been published.