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 (no $5 equivalent).

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 + privacy fields (the same disclosure content as CWS applies) → submit. Reviews land within days; as with CWS, plan for up to a week.

CI flow: the kit’s submit script (pnpm submit) targets Edge when EDGE_PRODUCT_ID, EDGE_CLIENT_ID, and EDGE_API_KEY are present in the environment (it wraps publish-browser-extension; submit:dry validates credentials without uploading). The product ID comes from the Partner Center listing URL after you’ve created the listing once by hand.

The 72-day API-key expiry

The gotcha that silently breaks release pipelines: Edge Add-ons API keys expire 72 days after creation. Symptoms: the Chrome and Firefox targets 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 also 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 in .output/.
• Edge users can also install straight from the Chrome Web Store, but a native Edge listing installs without the “allow extensions from other stores” friction and gets you Edge’s own discovery surface.
• Staged rollout: Partner Center supports gradual rollout percentages on updates (verify current availability for your account tier in the Partner Center docs).