v0.13.0
The Stable update track is now fully functional. Installs that follow Stable releases move from one published MOS release to the next: the update agent fetches the release tag, checks it out, rebuilds the platform, and reports the installed version truthfully — comparing your installed version against the newest published release instead of tracking day-to-day branch changes.
Also in this release:
- Fresh installs now default to the Stable releases track, so a new server follows published releases out of the box instead of a development branch. Development checkouts sitting on a named branch keep following that branch, and any track you chose yourself is unchanged.
- Branch-track updates (Main/Staging) now recover cleanly even if the tracked branch's history was rewritten, instead of failing the update.
- Fixed the Updates screen layout so the track-switch button aligns with the track dropdown.
Full details in CHANGELOG.md.
Upgrading
From v0.12.0 on any track: Suite Manager → Updates → Update now. This is the first release that can be applied through the Stable track end to end.
Known limitations (beta)
Unchanged from v0.12.0: backups are manual and unencrypted, external packages are unverified, and MFA/passkeys are not yet available. Pre-1.0 MOS is intended for evaluation and non-critical use with independent backups.