Releases & Updates
WPLM can act as an update server for your software. Publish releases (version metadata + a protected file), and licensed clients query the update API to discover and download new versions.
Publishing a release
Section titled “Publishing a release”License Manager → Releases → Add New. A release records:
| Field | Purpose |
|---|---|
| Product | The WooCommerce product the release belongs to. |
| Version | Semantic version string (e.g. 2.3.0). |
| Channel | stable, beta, or rc. |
| Changelog | Release notes (markdown). |
| File | The protected artifact location. |
| File hash | SHA-256 of the artifact (integrity check). |
| Min app version | The minimum version that can upgrade from. |
The update API
Section titled “The update API”| Endpoint | Purpose |
|---|---|
GET /wplm/v1/releases | List published releases. |
GET /wplm/v1/updates/check | A licensed client checks for a newer version. |
GET /wplm/v1/updates/download | Token-gated download of a release artifact. |
Downloads are served through short-lived signed tokens, never a public path, and only valid licenses can check or download — so updates are gated by license status.
Client flow
Section titled “Client flow”- The client calls
/updates/checkwith its license key and current version. - If a newer release exists on its channel, WPLM returns the version, changelog, and a tokenised download URL.
- The client downloads via
/updates/downloadusing that token and verifies the file against the published SHA-256 hash.