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: docs/README.md
+5-4
Original file line number
Diff line number
Diff line change
@@ -508,10 +508,11 @@ Protocol is published to NPM under the `@mozilla-protocol/core` namespace/packag
508
508
1. Before you start make sure the project's [CHANGELOG.md][changelog] is up to date.
509
509
2. Update the package `version` number in [src/assets/package/package.json][package.json] (use [Semantic Versioning][semver] to determine what the new version number should be).
510
510
3. Update the package README [assets/package/README.md][readme].
511
-
4. Submit a pull request with your changes (or commit directly to `master` if you have permission). Once the changes have been merged to master:
512
-
5. Tag a new release. You can do this either using [Git tag][git-tag], or directly on the [GitHub website][releases].
513
-
6. Run `npm test` to run the build script and front-end tests. The package contents will be located in `./dist/assets/protocol/`.
514
-
7. If the build is successful and all tests pass, publish to NPM using `npm publish ./dist/assets/protocol/`.
511
+
4. Run `npm install` to update the package-lock.json file.
512
+
5. Submit a pull request with your changes (or commit directly to `master` if you have permission). Once the changes have been merged to master:
513
+
6. Tag a new release. You can do this either using [Git tag][git-tag], or directly on the [GitHub website][releases].
514
+
7. Run `npm test` to run the build script and front-end tests. The package contents will be located in `./dist/assets/protocol/`.
515
+
8. If the build is successful and all tests pass, publish to NPM using `npm publish ./dist/assets/protocol/`.
0 commit comments