Releases and Updates
Scope note (TADR-0042 / Wave 90.5): Licensing Platform is not a software distribution platform. Artifact upload, DownloadGrant redeem, signed download URLs, and a dedicated
downloads.<domain>customer portal are out of active licensing product scope. Historical ADR-0032 remains for history (superseded for licensing scope).
What still matters for licensing
| Concern | Guidance |
|---|---|
| ProductVersion | Lightweight licensing label bound to a catalog Product when a tariff uses SpecificVersion scope — not an installer, S3 object, or DownloadGrant |
| Version scope on a tariff | Whole product or a specific ProductVersion — orthogonal to CommercialTerm |
| Entitlement | Runtime license decisions use Product + validity + VersionScope (+ rules). They do not require ReleaseArtifact storage |
| Client check | Prefer Runtime validate / lease claims + JWKS verify for entitlement trust |
Exact OpenAPI shapes for catalog ProductVersion and tariff drafts: API Reference / Management OpenAPI.
What is not part of licensing happy path
- Downloads SPA /
downloads.<domain>as a required customer portal - ReleaseArtifact / DownloadGrant / signed artifact URL management in Console
- Treating Management
/api/v1/releases*distribution APIs as active product surface (routes return 410 Gone; schema may remain for expand-contract)
Software binaries may still be distributed by other systems outside this platform. Licensing does not own that workflow.
Boundaries
- Runtime is not on a critical path for artifact bytes.
- Do not publish private signing keys, Host layout, or internal broker wiring.
- SDK package versions and changelogs live in each public SDK repository — see SDKs.