Publish a component bundle
Publishes a component bundle as a new version, creating the registry component, owned by this project, on its first version.
The bundle must pass the automated checks: the definition schema, the module and its agreement with the definition, size limits, the panel module when the definition declares one, and the conformance suite. Only people who may publish paywalls in the owner project, and organization admins, can publish versions of an existing component. Publishing the same bundle again returns the existing version.
Guide: Publishing
Errors
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request | conformance_failed | When the conformance suite fails. |
| 400 | invalid_request | invalid_bundle | When another check fails. |
| 409 | conflict | publisher_required | Before a namespace is claimed. |
| 409 | conflict | version_already_published | When the version exists with other contents. |
| 503 | unavailable | component_checks_unavailable | When the conformance checks could not run. |
It can also fail with the errors every operation shares, such as unauthenticated; see Errors.
More in Component registry
- Retrieve the registry publisher
GET - Claim a registry namespace
PUT - List registry components
GET - Publish a project component
POST - Retrieve a registry component
GET - Update a registry component
PATCH - List a registry component's versions
GET - Retrieve a registry component version
GET - Update a registry component version
PATCH - Retrieve a version's file
GET - Review an install
GET - List installed components
GET - Install a registry component
POST - Retrieve an install
GET - Update an install
PATCH - Uninstall a registry component
DELETE
Something wrong or missing on this page? Tell us by email or on Discord.