Updates
Manage sovereign Core/package update policy and understand hosted-site package update capability.
Updates installs supported Micro CMS releases and records the result. The built-in Official source is the normal source for Core, first-party Resource Packs and first-party Extensions.
Solo Sites
A Solo Site owns its Core, Resource Pack and Extension update choices. Automatic update settings are available for the classes supported by the current installation.
Bridge Hosts
On an active Bridge Host, the normal combined update keeps Core and Bridge software aligned. Core Only remains available as an independent public-Core update path and is not blocked by Bridge licence, entitlement or Bridge recovery state.
A Core Only update does not repair a damaged Bridge installation. If Bridge remains unavailable afterwards, use Recovery → Bridge Recovery to restore the existing Bridge installation.
Execution Nodes
Execution Node updates are managed by the owning Bridge. A registered Node can use the Node + Core automatic-update policy offered for that Node.
Managed Sites
A managed Site does not control Host Core or infrastructure updates. It sees only the Resource Pack and Extension actions made available by Host policy. Where useful, packages are marked Managed by Host.
Update History
History distinguishes the type of executable update, including Core, Core Only and Core + Bridge, and records the final result.
If an update fails
Use the action shown by Updates or the authenticated Recovery Hub. Do not mix versions by replacing individual Core files by hand.