LicenPro
DocumentationPlatformReleases

Releases

Software version lines that licenses target and the update checker uses. Global list vs product tab, release levels, and lifecycle from draft to deprecated.

A software release is a version line under a product—e.g. 1.0.0 Stable or 2.0.0-beta. Every issued license references a release id so validation, entitlements, and update checks know which build channel applies.

Why releases matter in the lifecycle

  1. Product create — initial version seeds the first release (see First product).
  2. License create — operator picks softwareReleaseId in step 1 of the wizard.
  3. SDK validation — license payload carries release metadata; mismatched app version may fail policy checks.
  4. Updates — SDK update managers and /api/Updates/… compare client version to release catalog.
  5. Access matrix — grant members access per release row, not only per product.

Product Releases tab

Primary operator surface for version management inside a product workspace. The global Releases sidebar item shows the same data across all products you can access.

Click image to open full-resolution preview.

Release fields (typical)

  • Version string — semantic (1.0.0), pre-release (1.0.0-alpha.1), simple (1), or build-based (1.0.0.1) depending on wizard choice.
  • Release level — Stable (production), Beta, Alpha, RC—signals support expectations and update policy.
  • Status — Draft (hidden from end users) vs Published (visible in catalogs and license wizard).
  • Notes / changelog — operator-facing text shown on the release detail page and optionally in update metadata.
  • Entitlement sets — link sets that apply to this version line (see wizard step 2).
  • Artifacts — installers via Storage connectors (Google Drive, OneDrive, custom server, S3-compatible bucket) instead of large API uploads.

Operator workflow

  1. Open product → Releases tab (or global Releases list).
  2. Create release — step 1: versioning format, version number, release level, draft vs published.
  3. Step 2: pick entitlement sets that apply to this build.
  4. Step 3: attach files from storage or upload references.
  5. Step 4: changelog and release notes for support teams.
  6. Issue licenses against this release id before customers upgrade app builds.
  7. When deprecating, archive old release after migrating licenses or forcing an update channel.
Click image to open full-resolution preview.

Release detail page

Opened from a row in the releases table or global release list. Shows everything support needs for a single version line.

  • Header badges — versioning style (Semantic), level (Stable), and Published status.
  • Changelog & release notes — editable narrative for operators and customers.
  • Entitlement sets — which SKUs apply to this release.
  • Files card — linked storage artifact with cloud download action (e.g. Google Drive file).
  • Edit — update metadata without re-creating the release id (prefer new release for breaking version bumps).
Click image to open full-resolution preview.

Update package (one-click updates)

Attach a zip of your app folder as the release file to let licensed apps install this version with "Update & restart". When you publish, LicenPro hashes the zip (SHA-256) and signs it with the product's RSA key; the Update package card on the release page then shows "Ready for one-click update".

  • Main executable — the file at the root of the zip that is started after the update. Leave it empty to use the running app's executable name.
  • Mandatory update — users cannot postpone or skip it; once downloaded it is installed at the next start.
  • Minimum supported version — clients older than this must install this update.
  • Verify package — after replacing the file of a published release, verify it so it is hashed and signed again.
  • Audience — the card shows how many active licenses are offered the update. A license gets new releases when Receives new releases is on (the default for new licenses); Beta and other levels reach only apps on that channel.

Release files come from your storage connectors. App side: Auto updater.

Roles

  • Product owner / system Admin — create, edit, delete releases.
  • Assigned Member with matrix row — view permitted release rows; may activate licenses on allowed lines only.
  • Viewer — read-only per matrix.

API & SDK

Catalog routes on /api/Products/… and release-specific endpoints in catalog API. SDK: Updates & logging for license-aware update checks.