extension-publishing-and-distribution

name	extension-publishing-and-distribution
description	Prepare Chromium extensions for packaging, Chrome Web Store submission, Microsoft Edge Add-ons submission, and controlled release management. Use when assembling a release build, writing listing metadata, validating review readiness, or planning update rollout.

Extension Publishing and Distribution

Overview

Publish only built artifacts that reflect the real extension the user will install. Keep packaging, store listing, privacy narrative, and permission justification aligned so review does not surface surprises late.

Read these references as needed:

• references/packaging-and-release-checklist.md for release prep
• references/chrome-web-store.md for Chrome submission concerns
• references/edge-add-ons.md for Microsoft Edge Add-ons specifics

Core workflow

1) Package the distributable build

• Build into a clean directory with manifest.json at the root.
• Package that directory, not the source tree.
• Use scripts/package-extension.sh when you need a quick zip of the built output.

2) Prepare listing and review materials

• Write a concise store description that matches the real feature set.
• Document why sensitive permissions exist.
• Prepare screenshots or review notes that show the core user flow.

3) Validate privacy and permission narrative

• Make sure store listing language matches manifest capabilities.
• Keep privacy disclosures aligned with actual network and storage behavior.
• Avoid surprises such as undeclared remote dependencies or unexplained host scope.

4) Submit per store, not by assumption

• Use Chrome Web Store guidance for Chrome.
• Use Edge Add-ons guidance for Edge.
• Treat each store's review questions and metadata requirements separately.

5) Control rollout and updates

• Keep a repeatable packaging path.
• Record version changes and release notes.
• Re-test the built package after every manifest or permission change.

Strong defaults

• Release only from a reproducible build output.
• Keep a short review checklist with packaging, permissions, and smoke tests.
• Store screenshots and narrative should highlight the main user flow, not internal implementation.

Anti-patterns

• Uploading the source tree instead of the built extension.
• Writing permission explanations that do not match the manifest.
• Assuming Chrome and Edge listings use identical review language.
• Skipping a final load-unpacked smoke test on the exact packaged build.

Notes

• Primary references:
  • https://developer.chrome.com/docs/webstore/publish/
  • https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/publish-extension
  • https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/partner-center
• Re-check store documentation when review or submission flows change.