v0.3.51

Fixed

• API error toasts now show the backend's actual reason instead of API error: 400. The shared apiFetch helper threw new Error("API error: <status>") on non-2xx responses, discarding the {"detail": "..."} body that FastAPI populates with the real cause (e.g. Media directory does not exist: /downloads/TV, Path is not under any configured media directory, Job is not in error state, etc.). Now reads the response body, extracts detail (or assembles one from Pydantic validation errors), and surfaces it through the thrown Error — so the v0.3.50 toast on the "+ Add" form (and every other toast that shows e?.message) finally tells the user what went wrong.

Docker images

Pinned to this release:

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

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