verstak
/
verstak-browser-extension
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: clarify browser release tagging

This commit is contained in:
mirivlad 2026-07-13 05:03:14 +08:00
parent 4dd87dc8cc
commit a80a2b55e6
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -67,12 +67,12 @@ Publish the signed XPI and `updates.json` as the current GitHub Release:
VERSTAK_BROWSER_ENV=/path/to/.env npm run publish:github VERSTAK_BROWSER_ENV=/path/to/.env npm run publish:github
``` ```
The publisher reads the version from `package.json`. It requires an The publisher reads the version from `package.json` and requires an
authenticated GitHub CLI, a clean local `main` equal to `origin/main`, and a authenticated GitHub CLI plus a clean local `main` equal to `origin/main`. It
tag pointing at that commit. It creates and pushes the tag if needed, then creates and pushes the version tag if needed, then creates or updates the
creates or updates the GitHub Release. Re-running it for the same tag replaces GitHub Release. Re-running it for the same tag replaces the XPI and
the XPI and `updates.json` assets. `npm run publish:firefox` remains as a `updates.json` assets. `npm run publish:firefox` remains as a compatible alias
compatible alias for the same Firefox publishing flow. for the same Firefox publishing flow.
For an explicit version check, pass the current tag after `--`: For an explicit version check, pass the current tag after `--`: