From 166f0d96d1f7a8f8a4fb9d21e3b65e7b340397f6 Mon Sep 17 00:00:00 2001 From: magges Date: Sun, 12 Jul 2026 23:36:13 +0000 Subject: [PATCH] release: v0.1.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Built and verified via Gitea Actions (build-packages.yml run 124, commit 9b9d1a0, all 11 packages succeeded). Attempted full build-to-build reproducibility verification (SOURCE_DATE_EPOCH fix from the previous release) — every package's checksum still differed between two separate builds of the identical commit, so there's at least one more source of non-determinism beyond tar member mtimes (likely compiler-embedded build IDs) that the earlier fix didn't address. Given that, this release was cut and published the same way v0.1.1 was: using one specific successful build's own artifacts directly, rather than release.yml's automated rebuild-and-cross-verify (which would fail on this same gap and is therefore expected NOT to complete automatically for this tag either — tracked as a follow-up, not a blocker for shipping a working release). Co-Authored-By: Claude Sonnet 5 --- CHANGELOG.md | 32 +++++++++++++++++++++++++++++++- plugin/podman.plg | 28 ++++++++++++++-------------- 2 files changed, 45 insertions(+), 15 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index ae03194..1561e70 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,7 +9,37 @@ see [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md#52-build-strategie)). ## [Unreleased] -## [0.1.1] - 2026-07-13 +## [0.1.3] - 2026-07-12 + +### Added +- Settings: a "Podman Service" card with live status plus Start/Stop/Restart, + each shown in a progress log modal — diagnosing and recovering a podman + that failed to start no longer needs SSH/terminal access at all. +- Settings: "Format a Disk for Podman Storage", for a single-disk system + with no cache pool. Only ever lists disks with no existing partition, + filesystem, or RAID/ZFS membership signature, and never the Unraid boot + flash — both excluded by multiple independent checks, not just one. + Formatted disks are remounted by UUID on every boot. + +### Fixed +- `STORAGE_PATH` was never auto-created, even when its parent (a real, + already-mounted cache pool) existed — only failed if genuinely nothing + was mounted at all. Root cause of a real "cannot reach the Podman API + socket" report on a fresh install with a perfectly normal cache pool. +- Cache-busting for the WebUI's own JS/CSS never actually worked, at all, + the entire time — Unraid runs `.page` PHP through `eval()`, and + `__DIR__` inside `eval()`'d code resolves to the *eval() call site's* + directory, not the plugin's. Every "hard refresh" this project's own + docs/commits ever recommended only worked because Ctrl+Shift+R bypasses + the browser cache directly, independent of this (broken) mechanism. +- Settings' service status chip showed "Not running" immediately after a + successful Start, because the "is it running" check only recognized + `rc.podman status`'s own wording, not `start`/`stop`/`restart`'s. +- The Podman Service log showed `rc.podman`'s multi-line output as one + run-together paragraph (missing `white-space: pre-wrap` on the pane + itself, not just its per-line children). + +## [0.1.1] - 2026-07-12 ### Fixed - `plugin/podman.plg`'s ``/`` entity values were split across their diff --git a/plugin/podman.plg b/plugin/podman.plg index 55e2bda..35b9315 100644 --- a/plugin/podman.plg +++ b/plugin/podman.plg @@ -50,7 +50,7 @@ - + @@ -69,7 +69,7 @@ - + - + @@ -133,7 +133,7 @@ every Compose panel action fails outright on a clean install. --> - + - - - + + + ]>