Philipp Kewisch
Philipp Kewisch
The action uses `GITHUB_TOKEN` from the env. What you could try is intentionally making it empty (e.g. setting an empty string via `env` in the action). I'm using the token...
I've made some changes, can you let me know if this is still an issue with v1? It should pass with a warning that the add-on was not auto-signed.
Hi @Lusito, thanks for filing this issue! I think updating the docs here would be great, either in the README or a wiki page. We've recently added https://extensionworkshop.com/documentation/publish/distribute-pre-release-versions/ which provides...
For our purposes, anything that is a https link and has mime types working correctly should work. I'm not sure mime types are right for the actual zip/xpi files using...
> * How to create or update the updates.json. This must contain the just released version number and a link to the released file. There is info on this [here](https://extensionworkshop.com/documentation/manage/updating-your-extension/)....
Also `January 12th - 6 months`, to be complete.
Related, `6 months after January 12th` would also be nice as an alias
I actually have a working patch for this, it just needs polish and some design decisions. All the developer really needs to do afaik is open gcli and enter e.g....
That is indeed handy, but my profile is 1GB large, and I don't want to copy that around each time I test an add-on.
If you don't believe this feature is useful I don't have any bad feelings if you want to close this. I am fine just keeping the WiP patch applied locally...