Adding a "extension publish" command

[vict0rsch]

I don't know if that's feasible for the Chrome Web Store but it should be for Firefox's: it would be great to automate the publication process from the CLI instead of going to the stores' websites

[cezaraugusto]

hey @vict0rsch that's planned for next year but probably integrated with a third-party service/library for the distribution step. by the way, I'm curious to know your thoughts on how this could look like in the future

[vict0rsch]

Beyond the technical details, I think the main challenge will be to provide an interface to update other fields than the package files. Ideally there could be a JSON / YAML / else interface where we can parameterize the various store params / descriptions / path to files. That would however come with a sync issue in case the user changes a field (ext description for instance) from the UI.

This means I think the first step would be something like a CLI with 3 steps that only focuses on the package update:

1. (optional) build + zip + zip source
2. Release description (mandatory I think for FAO)
3. Whether to include the source zip (mandatory for FAO if a bundler / minifier / obfuscater is used)

$ extension publish --chrome --firefox
> Do you want to build & zip? [y/N]: y
> Do you want to include the source files (mandatory for Firefox Add-Ons) [y/N]: y
> Update description (mandatory for Firefox Add-Ons): New publish feature, see github for more details