|author||avm99963 <email@example.com>||Sat Aug 08 15:40:39 2020 +0200|
|committer||avm99963 <firstname.lastname@example.org>||Sat Aug 08 15:51:58 2020 +0200|
Change the release system to a tag-based system Before, releases were created by commiting a change to the manifest.json file which updated the "version" field. This commit changes this procedure by generating the version strings directly in the release.bash script with the "git describe" command, based on annotated Git tags. Change-Id: I4de4e1040b7e9d22b4d3c8df9c0870989d966c49
When the code in the
master branch is considered to be stable, a release can be made. This is the procedure:
vx, where x is the extension's version number for that release) by running
git tag -a vx -m "vx". Note that the tag should be an annotated tag and not a lightweight tag, and it must be pushed to Gerrit after being created.
If during this process the release wasn't approved by Google or an issue was found during beta testing, a new release which fixes this should be created.
To create a zip file with the contents of the extension, which can be uploaded to the Chrome Web Store, run
bash release.bash. You can also use
bash release.bash --channel=beta to include a beta label in the extension name and version of the resulting zip file.
The ZIP file will contain a manifest.json file with the according version name, and will be located in the
You can also get information about how to use the
release.bash script by running
bash release.bash -h.
The beta channel is available here.