[Do not merge] Packaged v1.2.0 zip for Chrome Web Store upload#21
Closed
ShiosOS wants to merge 1 commit into
Closed
[Do not merge] Packaged v1.2.0 zip for Chrome Web Store upload#21ShiosOS wants to merge 1 commit into
ShiosOS wants to merge 1 commit into
Conversation
Co-authored-by: Julius Walton <ShiosOS@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This branch exists only to deliver the freshly built Chrome Web Store package — do not merge it (
*.zipis gitignored onmainon purpose).github-pr-reverse-comments.zip(v1.2.0, 15 files, ~17 KB) was built frommain(d885831) withnpm run build.How to get the zip
Download it from this branch:
https://github.com/ShiosOS/github-pr-reverse-comments/raw/cursor/chrome-store-zip-d7f1/github-pr-reverse-comments.zip
Then upload it at the Chrome Web Store developer dashboard.
Why the release pipeline didn't produce this automatically
The
v1.2.0release workflow run failed in the AMO signing step withUnknown JWT iss (issuer)— theAMO_JWT_ISSUERsecret doesn't match a valid addons.mozilla.org API key. Because that step failed, the workflow never reached the Chrome Web Store upload or the GitHub Release step. The CWS secrets (CWS_EXTENSION_IDetc.) are also not configured yet, so the CWS publish step would have been skipped anyway.Close this PR once the zip has been downloaded/uploaded.