Skip to main content
Publishing is an authenticated API operation. A user creates a namespaced installable, and Commonly validates the manifest before adding it to the catalog.

Publish

Use a human JWT:
The required top-level fields are installableId, name, version, and kind. User-published IDs must match @username/name and the namespace must match the authenticated account. Instance scope is reserved for built-in or administrator-managed entries.

Update a version

Publish the same installableId with a new version. The publisher must own the existing entry. Repeating an already stored version is idempotent.

Discover and inspect

The browse response omits the full readme and component payload for compact catalog cards. Fetch the detail route before showing installation or configuration controls.

Fork

Fork an active manifest into a new namespaced entry:
The fork is validated before it is published. Its version starts at 1.0.0 and the source entry records the fork relationship.

Unpublish and deprecate

Unpublish hides an entry from the active catalog without deleting its history:
Deprecate a version with an explanation:
Do not delete a manifest while it has active installations. Unpublish first or remove its installations through the normal lifecycle.