CasaOS Install v0.4.39

No functional code changes since v0.4.38. Re-pins the component releases to the commits now merged into their fork main branches:

• CasaOS LocalStorage v0.4.27 → v0.4.28 (commit fc5bbd3): republish from main after the boot fixes were merged (CasaOS-LocalStorage #10). Binary sources byte-identical to v0.4.27; the repository CHANGELOG now carries backfilled v0.4.26/v0.4.27 entries plus the v0.4.28 republish note.
• CasaOS AppManagement v0.4.19 commit pinned from PR-branch tip bd428f9 to the merge commit 40f2a6f (identical tree) — also the commit of the first tagged release of the fork (CasaOS-AppManagement v0.4.19).

Core packages and the compatibility overlay are republished with the matching v0.4.39 marker.

Verification

• Republished core tarballs byte-identical to v0.4.38 (digests equal the installer's embedded constants, unchanged).
• AppManagement v0.4.19 tarballs reused verbatim; git diff bd428f9 40f2a6f on the AppManagement fork is empty.
• v0.4.39 overlay differs from v0.4.38 only in the fork-release marker.
• LocalStorage v0.4.28 published by the fork release workflow; git diff v0.4.27 v0.4.28 shows only the CHANGELOG.md change.

v0.4.38

Supersedes v0.4.37 with a fix for the crash loop found in the first reboot test: the AppManagement storage-recovery sweep called SetStatus with a context carrying no event properties, so PropertiesFromContext returned a nil map and the service panicked every ~5s. AppManagement v0.4.19 (commit bd428f9) wraps the sweep context with common.WithProperties and adds a nil-map guard in SetStatus. Core republished unchanged from v0.4.37; overlay carries the v0.4.38 fork-release marker.

CasaOS Install v0.4.37

Full fork bundle with CasaOS LocalStorage v0.4.27 (restores all persisted mergerfs mounts during the before-docker init step, so /DATA is ready before Docker starts) and AppManagement v0.4.18 (starts apps abandoned because storage was not ready at boot, while respecting apps the user explicitly stopped). Core republished unchanged from v0.4.36; overlay carries the v0.4.37 fork-release marker.

CasaOS Install v0.4.36

Full fork bundle with CasaOS LocalStorage v0.4.26 (keeps restoring mergerfs mounts until source disks appear; fails loudly with offending entries on non-empty merge mount points; surfaces last restore failure in the merge status endpoint). Core and AppManagement republished unchanged from v0.4.35; overlay carries the v0.4.36 fork-release marker.

CasaOS Installer v0.4.35

Fixed\n\n- Supersedes v0.4.34 with exact 64-character SHA-256 values for every architecture.\n- Corrects the amd64 and arm/v7 AppManagement values that were truncated in v0.4.34.\n- Publishes the compatibility overlay with the matching v0.4.35 release marker.\n\n## Included components\n\n- CasaOS core v0.4.28\n- CasaOS UI v0.4.30\n- CasaOS LocalStorage v0.4.25\n\nAll seven platform package digests and the embedded installer constants were independently verified before publication.

CasaOS Installer v0.4.34

Fixed\n\n- Corrected the installer SHA-256 values for the fork packages. v0.4.33 published new package contents while retaining the previous release digests, causing upgrades to fail during checksum verification.\n- Republished the compatibility overlay with the matching v0.4.34 release marker.\n\n## Included components\n\n- CasaOS core v0.4.28\n- CasaOS UI v0.4.30\n- CasaOS LocalStorage v0.4.25\n\nAll amd64, arm64, and arm/v7 package digests were verified before publication.

CasaOS Install v0.4.33

CasaOS Install v0.4.33\n\nThis full fork bundle advances the coordinated CasaOS components after the previous v0.4.32 release.\n\n### Included changes\n\n- CasaOS core v0.4.28: use explicit systemd power actions and return power-command failures from the API (CasaOS #26).\n- CasaOS UI v0.4.30: keep the shutdown view stable after success and surface power failures (CasaOS-UI #15).\n- Preserve CasaOS LocalStorage v0.4.25 and the other component pins from v0.4.32.\n\n### Verification\n\n- Platform-neutral amd64, arm64, and arm/v7 bundles assembled from the exact component lock.\n- SHA-256 checksums included for all release assets.

CasaOS Install v0.4.32

CasaOS Install v0.4.32

This full fork bundle pins CasaOS LocalStorage v0.4.25, which restores persisted mergerfs mounts before creating default /DATA directories. Updates and service restarts no longer race directory creation against merged-storage restoration.

The bundle includes amd64, arm64, and arm/v7 packages, the compatibility overlay, the exact component lock, installer checksum verification, and the release manifest.

CasaOS Install v0.4.31

Highlights

• Publish the full fork bundle with CasaOS core v0.4.27, CasaOS UI v0.4.29, and CasaOS LocalStorage v0.4.24.
• Add host-level SMB zeroconf discovery through Samba mDNS/DNS-SD and Windows Web Service Discovery.
• Install Avahi and wsdd opportunistically while keeping installation and upgrades successful when optional packages are unavailable.
• Configure only the LAN discovery ports required for mDNS and WS-Discovery; SMB1 and legacy NetBIOS ports remain disabled.

Verification

All amd64, arm64, and arm/v7 archives were built from clean detached worktrees pinned to the component lock. SHA-256 values in install.sh, checksums.txt, and install.sh.sha256 were verified against the generated release assets.

CasaOS Install v0.4.30

CasaOS Install v0.4.30

This full fork bundle includes the latest CasaOS core, UI, and LocalStorage components and verifies every fork-owned package with SHA-256 checksums.

Component releases

• CasaOS v0.4.26
• CasaOS UI v0.4.29
• CasaOS LocalStorage v0.4.24

Included pull requests since v0.4.29

• CasaOS-LocalStorage #7: create missing Documents, Downloads, Gallery, and Media directories when external merged storage is created while preserving system AppData behavior.

The unchanged Gateway, UserService, MessageBus, AppManagement, CLI, and AppStore components remain pinned to their previously released commits.