Marketplace versioning

Marketplace items carry a version so contributors and users can identify the catalog revision being published or installed. The available update and review workflow depends on the item type and contributor capabilities enabled for the account.

Set a version when publishing

When publishing a project to the Marketplace, provide the version requested by the form. The current project-publishing flow validates semantic-version-style values such as 1.0.0 and stores the version on the Store Item.

Before publishing an update:

• describe the changes and any migration or configuration requirements
• confirm that selected components, dependencies, and provider assumptions are still valid
• run the available build and deployment checks for the project
• verify that protected environment values are not included in the published asset

Installing an updated item

Review the new version and its requirements before installing it into a project. An update may change component defaults, dependencies, VM composition, routes, or deployment settings. Existing project state is not automatically equivalent to a newly created project from the updated item.

Runtime rollback is separate

Component deployment rollback uses successful deployment history and the project deployment workflow. It is separate from publishing a new Marketplace item version.

See Contributor Guide, Creating a Store Item, Build Reviews, and Deployments for the related workflows.

Current limits

• A universal contributor version-management screen is not currently documented as available for every account or item type.
• Review, approval, monetization, and payout behavior depend on the enabled Marketplace workflow.
• Always follow the version and listing status shown by the product before treating an item update as available to users.