-
v0.10.9 — two fixes to the application backup/update path
Release / version (push) Canceled after 0sRelease / frontend (push) Canceled after 0sRelease / linux (amd64) (push) Canceled after 0sRelease / linux (arm64) (push) Canceled after 0sRelease / windows (push) Canceled after 0sRelease / macos (push) Canceled after 0sRelease / release (push) Canceled after 0sBuild and Push Docker Image / build-and-push (push) Canceled after 0sLastSkywalker released this
2026-09-06 11:21:19 +03:00 | 65 commits to main since this release-
Applications sharing only a name prefix are no longer merged into one card
when they are distinct file-backed compose projects (CasaOS names every
store app big-bear-). Merging them hid same-named services and let an
update of one project rewrite another project's compose file. The plan also
refuses any card that still spans several compose projects — the executor
must never be handed a multi-project job. Dokploy grouping is unchanged. -
A node could not leave :latest after switching to the beta channel. The
controller carried NODE_STATS_IMAGE in its own environment, and compose gives
the process environment priority over the stack .env — so the value the
controller was created with shadowed every later .env update. The controller
no longer receives the variable and strips it before invoking compose; the
.env it maintains is the single source of truth.
Both reproduced from a live host and verified there.
Downloads
-