v0.3.136
Fixed
- Newly-converted items still showing the NEW badge despite v0.3.132/.134/.135. Root cause: the Scanner UI computes
is_newfrom thenew_detected_attimestamp (scan.py:1221), not from theis_newcolumn the prior heals were clearing — theis_newcolumn turned out to be vestigial UI-side. For Sonarr→Shrinkerr pipelines completing within 24h of the original h264 drop,new_detected_atwas preserved through the worker's rename UPDATE and the badge stayed lit. Fix: also setnew_detected_at = NULLin all three worker post-conversion UPDATE sites, plus a one-shot startup heal that clearsnew_detected_aton every row already flaggedconverted=1.
Docker images
Pinned to this release:
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.136 # portable (amd64 + arm64, CPU)
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.136-nvenc # x86_64 + NVIDIA GPU (NVENC)
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.136-edge # as above but ffmpeg master
docker pull ghcr.io/i-ial9000/shrinkerr:0.3.136-edge-nvencFloating tags (:latest, :edge, :nvenc, :edge-nvenc) track the most recent release of each lineage.