MarketHub
My Packages
The My Packages section gives publishers a complete view of every package in their portfolio — across all statuses — with actions for submitting, editing, versioning, and withdrawing packages.
Package Status Lifecycle
| Status | Description | Visible to Public? | Available Actions |
|---|---|---|---|
| Draft | Package is being prepared — not yet submitted for review | No | Edit, Submit for Review, Delete |
| Submitted | Awaiting admin review; automated security scan has run | No | View, Withdraw Submission |
| Under Review | Assigned to an admin reviewer — review in progress | No | View (read-only) |
| Published | Live on the marketplace | Yes | Edit Listing, Publish New Version, Delist |
| Rejected | Admin rejected — feedback provided | No | View Feedback, Edit, Resubmit |
| Delisted | Removed from public marketplace | No | Relist (resubmit for review), Archive |
Publishing a New Version
To publish a new version of an existing package:
1
Export from InstallHub
Use InstallHub to export the updated artifacts with the new version number. Download the updated package file.
2
Upload Package File
In My Packages, click "Publish New Version" for the relevant package. Upload the new package file from InstallHub.
3
Write Changelog
Add changelog text for the new version. Describe what changed, what was fixed, and any breaking changes.
4
Submit or Save as Draft
Submit for review (enters admin queue) or save as Draft for later. The currently published version remains live while the new version is under review.
Package Edit vs New Version
| Change Type | How To Make It | Review Required? |
|---|---|---|
| Update description, screenshots, or tags | Edit Listing — no new package file needed | No — changes live immediately |
| Update pricing (Free ↔ Paid) | Edit Listing — pricing section | Yes — pricing changes require admin approval |
| Update package artifacts (new/changed workflow, form, etc.) | Publish New Version — requires new package file | Yes — security scan + admin review |