v0.3.54

Fixed

• Completed-job VMAF score showed a trailing 0 (e.g. 96.9 (Excellent)0). The expanded job report renders {job.vmaf_uncertain && (<warning>)} to show the measurement-suspect ⚠ marker on flagged scores. vmaf_uncertain comes from a SQLite INTEGER column (0 or 1) — the TypeScript type declares it as boolean but the wire value is numeric. 0 && (...) evaluates to 0, and React renders numeric zero as literal text (it only suppresses false/null/undefined, not 0). Coerced with !! so the falsy branch returns false and renders nothing. Other VMAF render sites (EstimateModal, EventTimeline, FileDetail, DashboardPage) already guarded correctly via != null checks or if statements; only the one expanded-report path was bare-truthy.

Docker images

Pinned to this release:

docker pull ghcr.io/i-ial9000/shrinkerr:0.3.54         # portable (amd64 + arm64, CPU)
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.54-nvenc   # x86_64 + NVIDIA GPU (NVENC)
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.54-edge    # as above but ffmpeg master
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.54-edge-nvenc

Floating tags (:latest, :edge, :nvenc, :edge-nvenc) track the most recent release of each lineage.