सीधे कंटेंट पर जाएँ
14 दिन का मुफ़्त ट्रायल, कार्ड नहीं चाहिए9 भाषाएँ176 व्यवसाय प्रकार · 50 ऐप
HI· USD
लाइव डेमो आज़माएँमुफ़्त ट्रायल शुरू करें

यह पेज अभी हिन्दी में उपलब्ध नहीं है, इसलिए इसे अंग्रेज़ी में दिखाया जा रहा है।

Versioning and compatibility

Every upload needs a newer version, a plugin keeps its id, compatibility is shown before buying, and documented plugin APIs stay stable within the 2.x line.

  • about 6 min
  • Every upload is newer (semver) than the live version. A version number can be reused only when that earlier upload failed the checks, was rejected or withdrawn. A plugin keeps its id across versions; older approved versions stay signed.
  • Updates: workspaces see Update to x.y.z, which re-installs the newest approved release. Widgets keep the owner's values — keep field keys stable.
  • Compatibility: a listing names the apps it needs and a minimum platform version (APP_VERSION in src/lib/modules/registry.ts, 2.6.0 today). The workspace shows what is missing and the Buy button stays disabled until it is met.
  • Stable for 2.x (plugins): the module.json fields, the SDK (@/lib/plugins/sdk), hook / filter / widget signatures (@/lib/plugins/types), callPluginAction, the /admin/<id> route contract, the pluginStore key layout and the settings key plugin_<id>. Hook names follow the webhook catalogue: events are added, never renamed; a removal is announced one minor version ahead.
  • Deprecation: a deprecated field or function keeps working for one minor version and is logged once per process ([plugins] deprecated: …). Remove it in your next release.
Your changeBump
Bug fixes onlyPatch: 1.2.0 → 1.2.1
New settings, widgets or hooks (defaults merge; saved values win)Minor: 1.2.0 → 1.3.0
Stored data changes shape (ship a lazy migration)Major: 1.2.0 → 2.0.0
Lazy migration recorded in pluginStore
const store = pluginStore("site-visits");
if (!(await store.get<boolean>("migrated:2", false))) {
  // transform old rows in small chunks here, then:
  await store.set("migrated:2", true);
}
Not supported for plugins today — do not build on them: plugin pages in the customer portal or on the public site, record tabs on core detail pages, new page-builder block types, new entity-registry entries, adding ids via dashboard.widgets, signatures for packages installed directly under System → Apps → Plugins (sha256 only) and a runtime isolate.

Written from: docs/PLUGIN-DEVELOPER-GUIDE.md, src/lib/modules/registry.ts, src/lib/plugins/sdk.ts, docs/DEVELOPERS/SUBMISSION-GUIDE.md, docs/MARKETPLACE.md, src/lib/marketplace/core.ts, src/lib/marketplace/store.ts