v0.5.32

[0.5.32] - 2026-10-18

Components: CasaOS v0.4.76. Unchanged from v0.5.31: CasaOS-UI v0.4.90, CasaOS-AppManagement v0.4.69, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Fixed

• The refresh of Debian 11 no longer stops on the security updates that moved to the archive. The security index of bullseye on security.debian.org still lists packages whose files are gone (404), so apt-get dist-upgrade failed on a box whose sources still named it, and the guide told you to edit them. The refresh now reads those lines as archive.debian.org/debian-security in the temporary sources it writes (your own files are never changed, and it checks they come back byte for byte), and says what it moved. When a download still gets a 404 from security.debian.org the refresh stops with the hint security_archive_gap.

v0.5.31

[0.5.31] - 2026-10-18

Components: CasaOS v0.4.75, CasaOS-UI v0.4.90. Unchanged from v0.5.30: CasaOS-AppManagement v0.4.69, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Added

• The assistant for optional modules, casaos module list|plan|install|remove|status, a subcommand of the core, with its API (/v1/sys/modules) and a Modules page in the dashboard. A module is a service in a repository of its own that you install only if you want it: the release carries a catalogue that pins each module's tag, commit and the checksum of its archive, the assistant downloads only that archive, writes only the files the module declares (its program, its one service unit and a sample configuration), and records them so that Remove takes away exactly those. The installer gains --module <name>. No module is offered by this release: the catalogue is empty until the first module (virtual machines) has been proved on real machines, so the dashboard shows nothing new and nothing changes on your box.

Changed

• Package updates, backups and the upgrade of the operating system wait while a module is being installed or removed, and the other way round.
• casaos-uninstall removes the installed modules first and says what stays (the packages they needed and their data).

v0.5.30

[0.5.30] - 2026-10-18

Components: CasaOS-UI v0.4.89. Unchanged from v0.5.29: CasaOS v0.4.74, CasaOS-AppManagement v0.4.69, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Added

• The page of the upgrade of the operating system, in the Operating system window, for the beta that v0.5.29 brought (it is still off by default; the page shows its switch). It follows the state of the upgrade and offers exactly the buttons the core says are valid: the refresh of Debian 11, the rehearsal and the hop (a window with the safety net, the name of the machine typed again, the acknowledgements, and what the plan removes and puts aside), the restart, go on, call off, close, take over by hand, and the word that closes a machine that is half upgraded. It says in plain words where the upgrade stands, with its block and progress, whether the point of no return is behind, and what stands in the way of the restart. While the machine restarts it says so, and after fifteen minutes it sends you to the machine's screen with the backup folder, the log and the commands you will need. English and French. Take a snapshot first: there is no way back from the point of no return except that snapshot.

Changed

• The restart and shutdown buttons of the top bar now say why they are refused while an upgrade of the operating system works on the machine, or while something that stands before its restart is not well.
• The window no longer says that ReCasaOS cannot upgrade the operating system for you yet, where the upgrade can be run.

v0.5.29

[0.5.29] - 2026-10-17

Components: CasaOS v0.4.74, CasaOS-AppManagement v0.4.69. Unchanged from v0.5.28: CasaOS-UI v0.4.88, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Added

• An upgrade of the operating system from Debian 11 to Debian 12, as a beta that is off by default and has no page yet: it is driven over the API. It is switched on by a file, /etc/casaos/os-upgrade.beta, or by POST /v1/sys/os/upgrade/beta; a machine that never switches it on is unchanged. It follows the procedure that Debian documents, in a transient systemd unit that the core starts: first a refresh of Debian 11 to its last state, then a rehearsal that stops short of the point of no return and puts the machine back, then the hop. Before the point of no return, whatever stops is undone: the sources and the timers of apt are put back. After it nothing is undone and the repair is a click of yours (go on), or the run's own text to follow by hand. The restart is always your click, and is refused while something that stands before it is not well (an /etc/fstab mount whose disk is not there). After the restart the core checks the machine and judges it against the notes it took before. Take a snapshot first, and be at the console when it restarts: there is no way back from the point of no return except that snapshot. The guide is docs/os-upgrade-beta.md in the CasaOS repository; it says what is proven (the commands were measured on a guest that booted, the machinery around them was not) and what each state means.
• The core reads the manifest of a module (/etc/casaos/modules/<name>.json), and the readiness report of the upgrade refuses a machine that has a module installed, naming it. Nothing installs a module yet.

Changed

• While an upgrade of the operating system works on the machine, the restart and the shutdown of the dashboard are refused (os_upgrade_open), the alerts about the apps' containers are kept quiet, and the automatic updates, the update button and the update of Docker say that the machine is busy. Backups and the automatic work of git apps are held the same way: CasaOS-AppManagement v0.4.69 looks at the flag file /var/lib/casaos/os-upgrade/busy, and while it is there the scheduled backups and the five-minute check of git apps wait, and a push from a forge is answered 202 held; what you click yourself (a backup, a restore, a deployment) is not held. A folder it cannot read counts as an upgrade that is open.
• The systemd-run of the package and Docker updates now has a limit of 30 seconds.

v0.5.28

[0.5.28] - 2026-10-16

Components: CasaOS v0.4.73 (unchanged), CasaOS-UI v0.4.88. Unchanged from v0.5.27: CasaOS-AppManagement v0.4.68, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Added

• The virtual machine page, behind the Virtual Machines card that appears when the opt-in virtualization module is installed (CasaOS-VirtManagement, contributed by Vinz2168): the list of machines (drag to reorder, state, IP with a copy button), and for the one selected its actions, a console (noVNC, loaded only when a console is opened), CPU and memory, disks, CD-ROM, network and USB devices; creating a machine from an ISO or a disk image, deleting it, and the default storage folder. A box without the module never downloads the page. In English, Italian and French. Force off and Force reset ask for a confirmation, and Escape closes only the dialog on top.

Fixed

• An app whose icon address does not load no longer shows a broken image in the App updates list: it gets the same default icon as the app grid.
• The titles of the blocks of the upgrade runbook are said in French in a French window (the plan section of the Operating system window).

Documentation

• The CasaOS-UI README said the dashboard is a Vue 2.7 application; it is Vue 3.

v0.5.27

[0.5.27] - 2026-10-13

Components: CasaOS v0.4.73, CasaOS-UI v0.4.87. Unchanged from v0.5.26: CasaOS-AppManagement v0.4.68, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Added

• The dashboard can show what an upgrade to the next Debian release would do on your machine, before anything is touched. In the Operating system window, a new Plan section (Debian 11 to 12 for now) asks apt to plan the upgrade in a private sandbox against the real mirrors: the sources it would write (the suites moved, the backports lines dropped, third-party sources such as Docker's put aside), the packages upgraded, added, removed and kept back, the disk room it needs and the download, and the packages the upgrade must never remove. The machine is not changed: the only thing written is the sandbox folder, removed afterwards. When the plan is not blocked it also writes, for the owner who wants to do the upgrade by hand with a snapshot and a console, a step-by-step runbook for exactly this machine, with stop lines, a point of no return and a way back before it. ReCasaOS still does not upgrade the system for you.
• A new proof, os-plan-proof, boots a Debian 11 guest, makes the plan, and checks that the machine did not change, that the plan matches the guest's own sources and that the runbook is sound, with a matrix of things made wrong on purpose (an unreadable source, a dead mirror, no room, a held lock, apt configuration that tries to run hooks).

Fixed

• The System packages window no longer hides its update button behind an older successful run. After an update had succeeded once, reopening the window showed that old result and no button until the check was run again.

Documentation

• CasaOS-UI now carries the Apache-2.0 LICENSE that IceWhale added upstream, with a NOTICE that says whose code is whose.

v0.5.26

[0.5.26] - 2026-10-12

Components: CasaOS v0.4.72, CasaOS-UI v0.4.86. Unchanged from v0.5.25: CasaOS-AppManagement v0.4.68, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Fixed

• The readiness report no longer says "ready, with things to look at" on every machine because of Docker's own package source. Docker's source is on every ReCasaOS machine and the upgrade puts it aside and rewrites it for the new release, so there is nothing for the owner to do: when it is the only source that is neither Debian's nor Ubuntu's, the report says so as a note, and the machine is plain "ready". The warning stays for any other third-party source, and now names only those; its text no longer mixes three cases in one paragraph, no longer lists the same file twice, and mentions mirrors of Debian or Ubuntu without a Release file only where it can apply.

v0.5.25

[0.5.25] - 2026-10-12

Components: CasaOS v0.4.71, CasaOS-UI v0.4.85. Unchanged from v0.5.24: CasaOS-AppManagement v0.4.68, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Added

• The dashboard can tell whether your machine could be upgraded to the next release of its operating system, and why not. In the Operating system window, a new Readiness section runs a check of about 55 points on Debian 11 and 12 and Ubuntu 22.04 and 24.04 (amd64): the identity of the system and whether it is a variant ReCasaOS does not cover (Raspberry Pi OS, Armbian, DietPi, Proxmox, OpenMediaVault, TrueNAS), whether a package operation or an app operation is running, an unfinished dpkg state, held packages, the apt sources (cdrom, release nicknames such as stable, proposed and backports suites, third-party sources, the format), DKMS drivers and Secure Boot, the boot loader, the disks, the free space, the memory, the network, Docker (its origin, a swarm, a daemon that is down, a newer version on offer, containers that would not come back, published ports) and the date of the last backup. It reads the machine and changes nothing on it: no cache is refreshed, no lock is taken, no service is started, and a point it cannot tell is shown as "could not check", never as fine. Each finding says what it found, what to do, and which are only warnings. The report can be copied as text. ReCasaOS does not upgrade the operating system yet: this is the first step, and a refusal here is what the upgrade itself will later refuse on.

Fixed

• The address shown at the end of an install is right again (ReCasaOS/CasaOS#21): on a box whose gateway.ini lists httpsport= before port=80, the installer read both lines as the port and printed http://192.168.1.15:https 80 with a bash syntax error. It reads the key port alone now, and the release workflow checks that on every release.

Changed

• A new proof, os-readiness-proof, boots a Debian 11 and an Ubuntu 22.04 guest, makes the machine dirty one way at a time (a held package, a release nickname in the sources, a stopped Docker, an unfinished dpkg journal, a full disk, and so on) and checks that the report names that cause alone, that it names nothing after the dirt is undone, and that the report changes nothing on the guest (the directories of dpkg, apt and ReCasaOS are hashed before and after).

v0.5.24

[0.5.24] - 2026-10-11

Components: CasaOS v0.4.70, CasaOS-UI v0.4.84. Unchanged from v0.5.23: CasaOS-AppManagement v0.4.68, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Added

• The dashboard updates Docker when its packages are on hold, if you tell it to. Until now a hold on docker-ce (an owner's deliberate act) only showed the terminal command that goes round it. The window now says that Docker's packages are on hold and asks for a confirmation of its own, a box to tick ("I know the packages are on hold and I want to update anyway"), then runs what apt-get install --only-upgrade --allow-change-held-packages would run. That command drops the hold of the packages it updates (dpkg marks them "install" again); ReCasaOS puts the hold back on the same packages when the update has ended, and the result says whether it did. A hold on any other package that the update would have to change still refuses the update, and a hold set or lifted after you confirmed makes the check ask again.

Changed

• The proof of the Docker update puts Docker's packages on hold on its Debian 12 leg (and docker-ce alone on every other leg, for the refusals): the check has to offer the update with the held packages named, a request that does not confirm the hold has to be refused, and after the update apt-mark showhold, the status and the log of the update have to agree that the hold is back.

v0.5.23

[0.5.23] - 2026-10-11

Components: CasaOS v0.4.69, CasaOS-UI v0.4.83. Unchanged from v0.5.22: CasaOS-AppManagement v0.4.68, CasaOS-UserService v0.4.31, CasaOS-MessageBus v0.4.29, CasaOS-LocalStorage v0.4.44, CasaOS-Gateway v0.4.30, Common v0.4.27, rclone v1.75.1.

Added

• The dashboard says where your system stands in its security support. A badge in the top bar appears when the free (Debian) or standard (Ubuntu) security updates of your operating system have ended, or end within 180 days; it opens a window with the date, the vendor's separate extended programme where there is one (Debian ELTS, Ubuntu Pro), the next release and the official upgrade documentation. Debian 11, which has had no free security updates since 31 August 2026, is the case that made it. It is read-only, it asks nobody anything, and it says plainly that ReCasaOS cannot upgrade the operating system for you yet: take a snapshot of the machine first, keep console access for when it does not start, and know that there is no automatic way back. Raspberry Pi OS, Armbian, DietPi, Proxmox, OpenMediaVault and every other derivative show nothing, because their support is not Debian's or Ubuntu's. One push message is sent per system, version and state (and only once a message really went out), when a channel is configured.