Andrew Williamson
Andrew Williamson
fixes #2451 Comments on this patch: It's large, but I couldn't see a way to split it into pieces. I attempted to add tests to cover the functionality in each...
follow-up for https://github.com/mozilla/web-ext/issues/2451 - to quote @rpl >This seems something that the AbortController may allow us to simplify and turn into a "more visually linear" async function, node-fetch seems to...
follow-up for #2451 - it's not going to support proxies at first, but to be feature comparable with sign-addon that's used for the signing api, it should support proxies too.
This tool needs to be updated to support the newer addons submission api on addons.mozilla.org. It might involve deprecating this project and starting afresh. Just logging the issue so there's...
the api response for addon detail contains an `icons` object, as well as `icon_url`, [since 2018](https://github.com/mozilla/addons-server/issues/7514) but looks like we forgot to file an issue to upgrade frontend to use...
The `no-node-access` eslint rule only currently activates on files where there is a direct import of a testing library function. The problem in our case is we wrap `screen` to...
fixes #2491 - and could address #2490 (at least in part) by clearly stating the addon id after it's available from AMO.
Background: AMO's submission API has three endpoints for creating a version from an xpi `Upload`: 1. POST to `/addons/addon/` to create a new add-on listing with the new version 2....
Right now the `addon-id` is saved in `.web-extension.id` _after_ the xpi has been downloaded. If the approval check times out, or the user cancels the wait before the timeout, the...
#2451 added support for signing add-ons via addons.mozilla.org/api/v5/addons/addon/ api endpoints (aka addon submission api), which an experimental `--use-submission-api`. Before it's released (or perhaps publicized, if it's released earlier) there are...