This document describes some instructions for maintainers. Other contributors and users need not be concerned with this material.
When setting up the repository on GitHub, configure the following settings:
- Under
Secrets
:- Under
Actions
, add theDOCKER_PASSWORD
repository secret with an appropriate value. - Under
Dependabot
, add theDOCKER_PASSWORD
repository secret with an appropriate value (e.g., that of the corresponding secret above).
- Under
- Under
Branches
, add a branch protection rule for themain
branch.- Enable
Require status checks to pass before merging
.- Enable
Require branches to be up to date before merging
. - Add the
Validate
status check.
- Enable
- Enable
Include administrators
.
- Enable
- Under
Options
, enableAutomatically delete head branches
. - Under
Pages
, change theSource
toGitHub Actions
and checkEnforce HTTPS
.
Follow these steps to release a new version:
- Bump the version in
[file:manifest.json]
and[file:package.json]
, runnpm install
to update[file:package-lock.json]
, and update[file:CHANGELOG.md]
with information about the new version. Ship those changes as a single commit. - Run
toast release
to build the extension. It will produce a file calledhashpass.zip
. - Upload the ZIP file to the Chrome Developer Dashboard and publish the new version.