Publishing commands
From Command Studio to a reviewed marketplace package: versions, review, updates and withdrawal.
Publishing takes a working Command Studio definition and turns it into a marketplace package. The pipeline:
definition (Studio)
│ Submit to marketplace (version + documentation + tags)
▼
pending review ──approve──▶ published (public listing)
│
└──reject (with reason)──▶ back to you, stays privateSubmitting#
From a definition in Studio, Submit to marketplace asks for:
- Version — must be semver (
1.0.0). An update must be a higher version than the currently published one. - Documentation — an overview, key features, use cases, setup instructions, required permissions and limitations. This is what installers read; write it properly.
- Category and tags — moderation, utility, welcome, fun or general; tags aid search.
The source is re-compiled at submit time. What gets published is a copy: the published version is stored immutably under its version number, and installs reference it. Later edits to your definition never mutate an already-published version.
Review#
A site admin approves or rejects. Rejections always carry a reason, which you see in Studio. Approval flips the package to the public listing (verified) and propagates the approved status to your definition.
Published packages can be unlisted — hidden from the catalogue while keeping existing installs working.
After publication#
| Event | What happens |
|---|---|
| A server installs | Its pinned copy is created from the published version; your install count rises |
You publish 1.1.0 | Installers see Update available; they pull it themselves |
| Someone forks | They get a detached copy; your package is unaffected |
| You withdraw | The listing disappears; existing installs keep working |
| Admin removes | Packages with active installs are unlisted rather than deleted |
Version discipline#
- Published versions are immutable — a fix means a new version.
- Updates must move the version forward; the submit form enforces semver and the bump.
- Rollback on the installer side pins an older published version — which still exists exactly as it was.
Deleting definitions#
A definition with active installs cannot be deleted — uninstall it from servers (or withdraw the package) first. This protects every server running your command from disappearing out from under them.