Edge (Partner Center)

Microsoft Edge runs Chromium, so the Edge package is the Chrome build with its own store pipeline. Registration on the Microsoft Partner Center is free.

Build and submit

pnpm build:edge   # local test build
pnpm zip:edge     # store zip

Manual flow: Partner Center → Microsoft Edge program → new extension → upload the zip from apps/extension/.output/ → fill listing and privacy fields (the same content as CWS) → submit. Reviews land within days; plan for up to a week.

CI flow: pnpm submit targets Edge when EDGE_PRODUCT_ID, EDGE_CLIENT_ID, and EDGE_API_KEY are present in the environment (submit:dry validates credentials without uploading). The product ID comes from the Partner Center listing URL after you create the listing once by hand.

Rotate the API key every 72 days

Edge Add-ons API keys expire 72 days after creation. Symptoms: Chrome and Firefox publish fine, the Edge upload starts failing with an auth error, and nothing about your code changed.

• Generate keys at Partner Center → Publish API (this shows the expiry date).
• Put a reminder ~10 weeks out, or rotate the key as part of every release cycle if you ship less often than quarterly.
• Rotating is instant: generate a new key and update the EDGE_API_KEY secret in CI; the client ID stays stable.

Edge-specific notes

• The Chrome zip is technically accepted, but use the zip:edge build; WXT targets Edge explicitly and keeps the output separate.
• Edge users can install from the Chrome Web Store too, but a native listing installs without the “allow extensions from other stores” friction and gets Edge’s own discovery surface.
• Staged rollout: Partner Center supports gradual percentages on updates; verify availability for your account tier.