flow-ext-publish

To publish a browser extension across multiple stores, you orchestrate preflight checks, asset verification, and cross-platform payload generation for Chrome Web Store, Firefox AMO, and Edge Add-ons. This workflow coordinates version alignment and handles platform-specific submission nuances automatically.

Preflight checks for browser extension publishing validate asset readiness, verify version alignment, and identify missing icons, promo tiles, or descriptions. The workflow routes missing assets to automated tooling to assemble them from project assets before proceeding to cross-platform submissions.

Yes, you can generate missing promo tiles and icons automatically during browser extension publishing. When preflight checks detect missing descriptions or assets, the workflow routes them to automated tooling to assemble or generate required assets from existing project files.

Browser extension publishing requires explicit user confirmation before uploading to stores. The workflow preserves guardrails and generates structured per-platform payloads, executing safe uploads only when explicitly authorized by the user during the final submission stage.

Handling platform-specific submission nuances for Firefox AMO and Edge Add-ons involves generating structured per-platform payloads from your project assets. The orchestration workflow adapts version data and asset formats to satisfy the unique submission requirements of each browser extension store.