Skip to content
This repository was archived by the owner on Dec 30, 2024. It is now read-only.

Commit c33647f

Browse files
committed
Update CONTRIBUTING.md
1 parent 06fc89c commit c33647f

1 file changed

Lines changed: 4 additions & 5 deletions

File tree

CONTRIBUTING.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -58,12 +58,11 @@ The E2E integration test suite requires a login cookie fixture in order to run a
5858

5959
## Release procedure
6060

61-
- Update the version in `package.json` and `src/assets/release_notes.html` (`manifest.json` is updated from `package.json` for Webkit automatically, but Firefox's `manifestv3.ffx.json` file in `utils/` must be manually changed).
62-
- To use the Docker build environment for packaging to `artifacts/` simply run `build.sh` in the project root. Note that `build.sh` artifacts will have UTC timestamps. The rest of these steps assume you're not using the Docker method.
63-
- Install prerequisites with: `pnpm install` or `npm install`
64-
- Use `pnpm build:pkg` or `npm run build:pkg` to generate deployables in the `artifacts/` folder when uploading to AMO or the Chrome addon store.
61+
- Update the version in `package.json`, `public/release_notes.html`, and `utils/manifestv3.ffs.json`. (`manifest.json` is updated from `package.json` for Webkit automatically, but Firefox's `manifestv3.ffx.json` file in `utils/` must be manually changed).
62+
- Commit and push to GitHub.
6563
- Tag a release on GitHub.
66-
- Add the zip to the release.
64+
- Wait for GitHub Actions to build. Download the artifacts from the completed CI job.
65+
- Add the zips to the release.
6766
- Release to the Firefox Add-ons site.
6867
- Log into the [Add-on Developer Hub](https://addons.mozilla.org/en-US/developers/).
6968
- Click "Edit Product Page" under "Chrome Shack" under "My Add-ons"

0 commit comments

Comments
 (0)