Kumar McMillan

The `sign` command is intended more for people who self-distribute their add-ons. In your case, why not just use the website? https://addons.mozilla.org/en-US/developers/addon/submit/distribution Is it because you need to put new...

Yeah, using web-ext to automatically put a new version in the AMO review queue seems like it could be useful to support automatic deployment (from a git tag or whatever)....

Even if we added a `web-ext submit` command, it would not be fully possible to automate submission. The `addons.mozilla.org` site always requires an editor to review the extension code which...

I removed the "submit for review" part of this issue title because [post-review](https://blog.mozilla.org/addons/2017/09/21/review-wait-times-get-shorter/) has landed! In other words, listed add-ons are now published ASAP without needing to pass human review....

Thanks for posting that @LinusU ! You may also want to check out this issue for the current limitations that `web-ext` has and how you could workaround them by working...

Agreed! Making it a new command would be the best approach. Publishing as a side effect of *signing* is weird and non-intuitive.

@birtles thanks for your help on this! Here are the pre-requisites: - `sign-addon` needs https://github.com/mozilla/sign-addon/issues/253 so that `web-ext submit` can share code with how `web-ext sign` already works - The...

Sorry about running into this. I think this is a dupe of https://github.com/mozilla/web-ext/issues/680 . You could test it by waiting a couple minutes and then checking the URL to see...

I believe the final URL to the file is not auth-protected so you can just download it

Can you consistently reproduce a 404? If so, can you attach a log with `--verbose` ?