Managing Product Releases

Automated builds and manual uploads both land in the same place — Admin → Licensing → Product Releases — and can be managed identically from there.

Manual Upload Still Works

You don't need a connected repository to ship a release. Create a Product Release, then upload a zip asset directly — useful for one-off builds, partner deliverables, or products with no Git history in the platform.

Editing a Release

The following can be changed at any time, even after a release is published:

Changelog — rich text describing what changed
Metadata — custom key/value pairs (e.g. build number, changelog URL)
Requirements — minimum versions of other modules or products this release depends on
Minimum Upgradeable Version — the oldest installed version allowed to upgrade directly to this release

Replacing the Asset

Upload a new zip to replace the release's downloadable file without creating a new version — useful for patching a bad build without bumping the version number.

Download Tracking

Every download increments that release's download count. The Downloads report (Admin → Licensing → Reports → Downloads) breaks totals down per version, so you can see adoption of each release over time.

Default Release & Pinning

The default release is what the Launcher and customer downloads serve. By default, the most recently published release is automatically the default — publishing a new version promotes it and demotes the previous one.

To keep an older version as the default (for example, to hold back a release while you finish validating it), open that release and choose Pin as Default. A pinned release stays the default even after newer versions are published — new releases are stored and available but do not take over automatically. Choose Set to Auto (Latest) to unpin and return to latest-wins behavior.

Managing Product Releases