adguardteam/go-webext

If you maintain a browser extension that ships across Chrome, Firefox, and Edge, you know the pain of logging into each store's developer dashboard separately to upload new versions and publish them. go-webext is a command-line tool that automates that entire process. Instead of manually clicking through three different web interfaces every time you want to release an update, you run a few commands and the tool talks to each store's API directly. The tool supports four main actions: checking an extension's current status, uploading a brand-new extension, uploading a new version of an existing one, and publishing it to users. It also handles Firefox-specific signing. You provide your credentials for each store through environment variables or a local config file, then issue commands like "publish this to Chrome" or "update Firefox with this zip file." For Chrome's newer API, you can even do gradual rollouts (say, pushing to 50% of users first) or request an expedited review. The primary audience is teams and individuals who ship browser extensions on a regular basis, think companies like AdGuard (who built this) that maintain ad-blocking extensions across all major browsers. It's especially useful if you've wired your extension builds into an automated release pipeline and want publishing to happen without human intervention. A solo developer who releases infrequently might find it overkill, but anyone managing multi-store releases on a cadence will save real time. One thing worth noting: the tool doesn't create new Edge listings for you, Microsoft requires that step to be done manually in their Partner Center. It can only update and publish extensions that already exist there. Chrome and Firefox, however, support full creation through the tool. The README also notes that Microsoft is shifting Edge authentication from long-lived secrets to shorter-lived API keys, so Edge users will want to use the newer v1.1 API path.