live one every install is serving, and one
other — waiting on review, withdrawn back to a draft, or rejected. Publishing overwrites
rather than accumulating, so there is no version to pick and nothing to promote. The version
a release is labelled with is your package.json version, read out of the bundle.
What a publish becomes
“A new contribution kind” means a kind the live release does not have — your first widget,
your first action, your first storage collection. A second widget is not a new kind. The
seven assistant blocks count separately, so your first skill is a new kind even when you
already ship tools.
Dropping a scope or a contribution kind never sends a release to review.
Release notes
Withdrawing a pending release
A release in review can be pulled back to a draft from the Releases page in the developer portal. The live release is untouched and the review timeline is kept. Publish again when you are ready and it re-enters review. Publishing while a release is still in review replaces that release rather than queueing a second one.What owners see
An approved release swaps intolive and every install picks it up on its next load; the
host re-reads its installs about once a minute while the dashboard is open. When the new
release asks for a scope an owner has not granted, their install renders