Product delivery
Upgrades
Move installs to newer versions, manually or in a maintenance window.
Upgrade by hand
Details on a product card lists its installs. When a newer version is available on the install's channel, Upgrade appears. Upgrading rewrites the installed resources from the new version and binds the install's recorded inputs again.
Change version picks a specific version instead, including an older one (a rollback).
Automatic upgrades
An install created with Auto-upgrade is upgraded by the platform's maintenance run, which only realm administrators can start. It upgrades an install only:
- inside its daily maintenance window (
HH:MM-HH:MMin UTC, overnight windows allowed), or at any time when it has none; - when it is not locked;
- when its linked products still fit (see Linked products).
The maintenance run acts with the installer's own access, so an automatic upgrade can never bring in something the installer could not install by hand. An install that cannot upgrade stays on its version and is reported; it never blocks the others.
What is refused
| Situation | Result |
|---|---|
| Install is locked | Refused until unlocked. |
| Version is not on a channel the install sees | Refused. |
| Upstream product at the wrong major in the project | Refused, naming the product. |
| Upstream major upgrade while a dependent has no matching version | Refused, naming the dependents. |
| A required input has no value | Refused. |