If you already run this distribution, this release is the one that repairs the in-app updater — and you have to install it by hand, once.
curl -fsSL https://github.com/inkly/CasaOS-Install/releases/latest/download/install.sh | sudo bashAfter that the dashboard's update panel follows this distribution on its own.
Why the updater never offered an update
It was watching someone else's releases. Four files shipped by CasaOS still carried alvins82's fork URLs, and one of them — the setup script inside this installer's compatibility overlay — wrote them into /etc/casaos/casaos.conf on every install, where CasaOS prefers them over its own built-in addresses.
So a host installed from here polled a feed whose newest release (v0.4.39) was older than what it was running, concluded it was up to date, and said so for good. Had the update ever fired, it would have fetched that fork's installer over this one. An installation made before today cannot repair itself, because the broken setting is exactly what the updater reads — hence the manual run above.
CasaOS now carries a test that fails if a shipped file and the built-in addresses ever disagree again, which is the check that was missing when the distribution was first retargeted.
Also fixed
- The gateway's health check against its own listener retried forever instead of ten times: the countdown ran through an unsigned integer, so the last decrement wrapped to 18 446 744 073 709 551 615. A listener that never answered left the gateway probing once a second rather than returning the error its caller expects.
Documentation
Every component repository now has a README that describes what that service actually does — its routes, where its data and configuration live, what this distribution changed in it, and how to build and test it. Each one was fact-checked against the code, which caught a fair number of confident inventions along the way.
Components
CasaOS v0.4.42, Gateway v0.4.20, CasaOS-UI v0.4.32, AppManagement v0.4.21, MessageBus v0.4.19, UserService v0.4.18, LocalStorage v0.4.29. The exact commits are in components.lock; every package the installer downloads is verified against a digest taken from the component's own release.