We need to determine:
@hstove Having trouble understanding what step in the GH workflow does the actual upload to the Chrome/FF store. Do the Chrome and FF stores reference our GCS bucket when users download the addon through their site?
Also, it doesn't seem like Chrome is requiring us to sign the plugin before uploading to GCS like Firefox does. If there is a signing step available for that process, I'd like to look into that as well.
The GCS bucket is not relevant to actually publishing on the stores - that's just our temporary workaround. Publishing to the stores will be a similar, but different process.
For Chrome, we can almost fully automate the publishing process from CI.
For Firefox, we already have the web-ext
integration setup, and it's publishing to our "unlisted" channel. Publishing to the "production" version of the store requires simply changing a flag to --channel listed
, but that still requires a human to log in and:
So I'm less bullish on automating the FF process, since it might cause more hassle
Should we assign @CharlieC3 here if he's the one mainly looking in this at the moment?
@CharlieC3 Mind providing an update here when you have a chance?
@markmhx No update as of yet, but will start on this ticket this week.
@hstove Do we need to provide any justifications here for the Chrome listing?