Extension store services
Extension store services
The family ships two flavours of extensions. Browser extensions
publish to three stores (Chrome, Firefox, Edge); VS Code
extensions publish to two marketplaces (VS Code Marketplace +
Open VSX). JetBrains was considered as a third VS Code-style target
and explicitly walked back — the family does not ship JetBrains
plugins. All five stores in this bucket are free or one-time-fee, no
card-on-file. Single consolidated decision:
decisions/architecture/distribution-and-queues-locked.md.
Browser-extension stores (oriz-*-ext)
| Service | Status | Role | Cost |
|---|---|---|---|
| chrome-web-store.md | active | ext-store-chrome | $5 one-time dev fee (sunk) |
| firefox-add-ons.md | active | ext-store-firefox | Free, no card |
| edge-add-ons.md | active | ext-store-edge | Free, no card |
CI flow per repo: build once → submit in parallel to all three.
Tools: web-ext for the
cross-browser package + AMO sign,
chrome-webstore-upload
for Chrome,
wdzeng/edge-addon GitHub
Action for Edge.
VS Code extension marketplaces (oriz-*-vsc-ext)
| Service | Status | Role | Cost |
|---|---|---|---|
| vs-code-marketplace.md | active | ext-store-vscode | Free, no card |
| open-vsx-registry.md | active | ext-store-openvsx | Free OSS, no card |
CI flow per repo: build .vsix → publish to VS Code Marketplace
via @vscode/vsce +
publish to Open VSX via
@vscode/ovsx (same
artifact). One build, two pushes — never three.
Walked back
| Store | Reason walked back |
|---|---|
| JetBrains Marketplace | Family ships VS Code extensions only. No JetBrains-IDE plugin in plan; adding the publish step pre-emptively would be over-coverage. Re-open if a JetBrains plugin is ever greenlit — see decisions/architecture/distribution-and-queues-locked.md "walked back" section. |
The publish matrix
Browser extension repo (oriz-*-ext)
├── build → dist/extension.zip (web-ext)
├── publish → Chrome Web Store (chrome-webstore-upload)
├── publish → Firefox AMO (web-ext sign)
└── publish → Microsoft Edge Add-ons (edge-addon action)
VS Code extension repo (oriz-*-vsc-ext)
├── build → dist/extension.vsix (vsce package)
├── publish → VS Code Marketplace (vsce publish)
└── publish → Open VSX Registry (ovsx publish)
Both flows use the same family pattern from
decisions/process/per-repo-ci-workflows.md.
Credentials originate at Doppler and
mirror to GitHub Secrets.