Available Updates Page #
The customer-facing page showing which products have updates available.
What Customers See #
For each product the customer has a license for, the page shows:
| Item | Description |
|---|---|
| Product name | Which product |
| Current version | Version the customer is currently running (from tracking data) |
| Available version | Latest version available for their license and channel |
| Update status | Up to date / Update available |
| Changelog | What changed in the available version |
| Download button | Click to download the update file directly from the portal |
| Rollback button | Access older versions |
How "Current Version" Is Determined #
The portal reads from the version tracking table, which is populated when client software checks for updates via the API. If the customer's software has never called the update API, current version shows as "Unknown."
Customers who install updates through the portal (not via auto-update) should also appear in tracking once their software next calls the API after updating.
The Download Button #
Clicking Download:
- Generates a signed HMAC download token (same security as the API)
- Begins the file download in the browser
- The download is logged in the Update Server download history
Download tokens generated from the portal are subject to the same token expiration settings as API tokens.
Rollback (Previous Versions) #
The Rollback button or link shows all available versions for the product, not just the latest. Customers can choose a specific older version to download.
This lets customers:
- Roll back to a previous version if an update broke something
- Download a specific version for testing or compatibility
Update Eligibility in the Portal #
Whether a specific version appears as "available" follows the same rules as the API:
- License must be active
- Version channel must match license channel or be lower (stable is visible to all)
- Rollout percentage must include this license
Note: The portal uses a slightly different rollout bucketing algorithm than the API. See Staged Rollout – Note on Two Code Paths for details.