Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: ci/cd creds for ext publishing #273

Merged
merged 2 commits into from
Jan 24, 2025
Merged

docs: ci/cd creds for ext publishing #273

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
686a173
docs: ci/cd creds for ext publishing
conorsch Jan 24, 2025
dacf9a8
satisfy linter
TalDerei Jan 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/ci-cd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,25 @@ Main merges will also deploy dapp on Firebase. Workflows can be [seen here](../.

If a release is made in the repo, the extension code will be submitted for publishing
to the Chrome Web Store. See more in [publishing](./publishing.md).

### Creds for publishing

Publishing to the webstore requires three (3) credentials to be present in CI:

1. Google app oauth client_id
2. Google app oauth client_secret
3. Google app refresh_token

If an extension publishing job fails with an HTTP 429, it's likely either:

1. unreviewed drafts in the developer web ui, or
2. an expired "refresh token" being used in CI

If you need to update 2:

1. Follow this guide: https://github.com/fregante/chrome-webstore-upload-keys
2. Download JSON file with client_id and client_secret (constituting 2/3 of the creds you need)
3. `node cli.js` in that repo, follow the interactive tool
4. Edit the CI secrets in this repo with the new client_id, client_secret, and refresh_token values

Then rerun the failed publishing job, and confirm it passes.