You publish an extension through an independent registry. A connector makes that registry usable inside a supported system. Your registry stays responsible for releases, packages and access rules.
Why this exists
Building an extension is only part of shipping it. Independent distribution also needs release metadata, package delivery, compatibility information, installation and updates. Rebuilding that path for every extension and every target system wastes effort.
ExtensionMesh separates the source of an extension from the integration with a particular system. That creates a reusable path without requiring one mandatory catalogue or operator.
Your path through ExtensionMesh
Create and package your extension
You keep using the tools, release process and package format required by the system you support.
Release through a registry
The registry publishes the extension metadata, compatible versions and package location needed by a connector.
A system-specific connector reads the source
The connector translates registry information into the discovery, installation and update mechanisms of the supported system.
Future releases use the same path
Publish another compatible release and the connector can make that update available without a separate manual delivery workflow.
What remains under your control
- Where packages and release metadata are hosted.
- Which extensions and versions your registry publishes.
- Whether packages are public, private, free or commercially licensed.
- Authentication, entitlement and availability rules of your registry.
- The systems and versions your extension supports.
What ExtensionMesh provides
ExtensionMesh defines the roles and integration boundaries needed to connect independent sources with supported systems. It is not intended to host every package, operate every registry or make publication decisions for extension creators.
What works today
The project is validating this model through its first connector, which targets Shopware. The shared registry conventions are still being extracted from that implementation, so a stable system-independent publication specification is not available yet.
What you can validate today
- Publish a conventional plugin repository through a release workflow that produces a validated ZIP, checksum and registry metadata.
- Use a seller-operated installation to publish digital-product ZIPs and provide entitled customers with registry access.
- Connect a public or private GitHub repository and synchronize stable release assets into a seller installation.
- Run the separate buyer and seller environments locally to exercise the complete publication, purchase, update and revocation flow.
These workflows are available for evaluation and contribution. Interfaces, packaging rules and setup steps may still change before the first stable release.
Continue with the registry model, read the GitHub publishing notes, or follow implementation progress in Extension-Mesh/shopware.