跳到正文
14 天免费试用,无需银行卡9 种语言176 种业务类型 · 50 个应用
ZH· USD
试用在线演示免费试用

此页面暂无简体中文版本,现以英文显示。

Review, release and install

A person reviews every passing version. Approval signs and publishes it; rejection comes with a reason. Plugins also wait for a platform release before workspaces switch them on.

  • about 7 min
  1. Upload in the portal: the checks run at once (checks_failed or in_review).

  2. A person reviews the report, what the extension can access, the data or code (plugins: every line), the texts and screenshots.

  3. Approved → the platform signs the exact package, the listing is published and you get an e-mail in your language.

  4. Rejected → the reason arrives by e-mail and in the portal; fix and upload again.

TypeInstall in the workspaceUninstall
ThemeBranding + site layout updated; the earlier look is savedSaved look restored if this theme is active
WidgetSigned definition copied into the workspaceRemoved; its blocks render nothing
IndustryWebsite starter applied in reset mode (old website backed up)Pages stay — they are the owner's content now
DocumentNew design under Documents (not default)Deleted unless it became the default
IntegrationScoped API key + webhook endpoint + signed app.installed callKey revoked, endpoint deleted, signed app.uninstalled call
PluginSwitched on when the reviewed version is in the running platform build; else “waiting for the platform release”Switched off (data kept)
Plugins run in-process, so they are never hot-loaded from an upload. The platform team ships the reviewed package with the next platform release; licensed workspaces are switched on once it is live (permissions and settings seeded then).

Written from: docs/DEVELOPERS/SUBMISSION-GUIDE.md, docs/DEVELOPERS/PLUGIN-SDK.md, docs/MARKETPLACE.md, src/lib/marketplace/store.ts, src/lib/marketplace/install.ts