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
Copy file name to clipboardExpand all lines: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -309,6 +309,6 @@ The project follows the same release process as the other libraries in the MetaM
309
309
310
310
7. Publish the release on npm.
311
311
312
-
-Be very careful to use a clean local environment to publish the release, and follow exactly the same steps used during CI.
313
-
-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]/`).
314
-
- Once you are confident the release contents are correct, publish the release using `npm publish`.
312
+
-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.
313
+
-Approve the `publish-npm` job (or ask somebody on the npm publishers team to approve it for you).
314
+
- Once the `publish-npm` job has finished, check npm to verify that it has been published.
0 commit comments