You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The publishing instructions in the README have been updated to reflect
changes introduced in #125. We forgot to update the README in that PR.
The release instructions should now match those in the module template.
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -132,6 +132,6 @@ The project follows the same release process as the other libraries in the MetaM
132
132
133
133
7. Publish the release on npm.
134
134
135
-
-Be very careful to use a clean local environment to publish the release, and follow exactly the same steps used during CI.
136
-
-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]/`).
137
-
- Once you are confident the release contents are correct, publish the release using `npm publish`.
135
+
-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.
136
+
-Approve the `publish-npm` job (or ask somebody on the npm publishers team to approve it for you).
137
+
- Once the `publish-npm` job has finished, check npm to verify that it has been published.
0 commit comments