Updates
Install supported releases, review history and recover update-source problems.
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.
Install An Update
Choose Install Update. Micro CMS downloads and verifies the release before changing the installed software. When the verified release needs no additional decision, installation continues automatically.
If the release requires a choice — such as Core Only versus Core + Bridge, a new Extension capability, a manual data change or a Resource Pack conflict — Updates stops at that decision and shows the available action.
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 when you intentionally need to update public Core without updating Bridge.
A Core Only update does not repair a damaged Bridge installation. If Bridge remains unavailable afterwards, use Recovery → Bridge Recovery for the existing installation.
Execution Nodes
Execution Node updates are managed by the owning Bridge. Choose Update Nodes when you want to start a Node update manually; Bridge refreshes each candidate Node before deciding whether it is current, eligible, deferred or needs attention. A registered Node can also 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 executable update type, including Core, Core Only and Core + Bridge, and records the result.
Update File Cleanup
Completed executable updates clean up eligible old update files automatically. If Clean Old Update Files is offered, use it to remove remaining update files that could not be cleaned up automatically.
Update Sources
Removing a custom update source removes that source configuration only. Installed packages and update history remain intact. If Updates reports that the official feed needs to be reset, use Reset Update Feed and confirm with the Owner password. Then check for updates again. Resetting corrects the update-source history; it does not reinstall Core or restore Site content.
If An Update Fails
Use Retry/Resume, the action shown by Updates, or the authenticated Recovery Hub. Technical details are available for update mismatches when needed; do not replace individual Core files by hand as the normal recovery path.