Publish a release

Take a draft through validation, review, and publish so customers can install it.

Create the draft

createComponentDraft takes a product code, a semantic version such as 1.0.0, a prompt, release notes, and files. Each file has path, optional target, fileType, language, and content.

Edit in Studio

Open /dashboard/platform/studio/[id]. Use the source editor to replace files. Each save needs the current revision and manifest hash and resets earlier evidence.

Validate

Run validation. Fix any failed check from the stored log, save, and run it again. The draft needs at least one renderable component, ui, block, or page file.

Submit for review

Submit. A review record is created with the validation evidence attached.

Decide

A reviewer with canManageProducts approves, or requests changes with notes of 10 to 4000 bytes. Request changes sends the release back to draft.

Publish

Publish the approved review. The release becomes stable and publishedAt is set. Confirm at /r/<code>.json.

If you change product price, license, or release notes after submission, approving fails with a message to choose Request changes. Do that, revalidate, and resubmit.

Create a product

Add a free or paid component to the catalog with a design system and license terms.

Sell a paid kit

Connect Stripe, price a product, and confirm a customer can buy and install it.

On this page

Create the draft
Edit in Studio
Validate
Submit for review
Decide
Publish