maggesandClaude Sonnet 5
166f0d96d1
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 <noreply@anthropic.com>
3.1 KiB
3.1 KiB
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning for the plugin version (independent of the bundled Podman/upstream package versions, see docs/ARCHITECTURE.md).
Unreleased
[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_PATHwas 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
.pagePHP througheval(), and__DIR__insideeval()'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, notstart/stop/restart's. - The Podman Service log showed
rc.podman's multi-line output as one run-together paragraph (missingwhite-space: pre-wrapon the pane itself, not just its per-line children).
[0.1.1] - 2026-07-12
Fixed
plugin/podman.plg's<URL>/<MD5>entity values were split across their own lines (<URL>\n&baseURL;/...\n</URL>) — Unraid's plugin manager passes that text straight into awget ... -O <name> <url>shell command without trimming it, so the leading newline broke the command in two:wgetsaw no URL argument at all, and the URL text ran on the next line as its own (failing) shell command. Every real Unraid plugin (verified againstunassigned.devices.plgon a live host) keeps<URL>...</URL>on one line — found by running the plugin installer's own CLI (scripts/plugin install) directly on a real Unraid host and reading its raw output, rather than trusting the webGUI's summarized install log.
[0.1.0] - 2026-07-12
Added
- Initial repository scaffolding: directory structure, documentation skeleton, CI workflow stubs, and community health files.
- Architecture documentation (
docs/ARCHITECTURE.md).