-
Notifications
You must be signed in to change notification settings - Fork 343
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.
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
Allow programatically signing from an xpi file #3241
Comments
I realized I can just |
We're in favor of allowing zip files to be signed. A more generic issue was filed at #3242, to offer a CLI option to do the same. I'm inclined to only accept zip files and not xpi files to avoid accidentally submitting a signed file again, but I am willing to consider xpi files if there is a compelling use case.
Patches are welcome! |
Might be worth rather checking for an existing signature, or failing on the server side if a signed file is uploaded. zip vs xpi is really just a file extension, so I don't think it makes a difference. I'll send a PR soon |
Is this a feature request or a bug?
Feature request
What is the current behavior?
Programmatically, the only way to sign is using
webExt.cmd.sign
, which also does a build. https://github.com/mozilla/sign-addon is deprecated, likely because it was included in utils/submit-addon.js. There doesn't seem to be a way to trigger a submission for an existing xpi.What is the expected or desired behavior?
If we add utils/submit-addon to exports, I'd be able to use it directly. I'm open to other ideas.
The text was updated successfully, but these errors were encountered: