Fixed
- Test Connection always failed with "URL and API key required" for Jellyfin (and inherited by v0.4.0 Emby). Root cause: the
PUT /api/settings/encodingsave handler only persistedjellyfin_url/emby_urlto the DB. The other 8 fields per server (*_api_key,*_user_id,*_path_mapping,*_scan_after_conversion,*_empty_trash,*_pause_on_stream,*_pause_stream_threshold,*_pause_transcode_only) were silently dropped by the handler — fields existed on the model and showed up in_ENCODING_DEFAULTSand the GET response, butupdate_encoding_settingsnever wrote them. Pre-existing for Jellyfin since it was added; Emby inherited the same gap. Effect:_get_*_settings()always returned an empty*_api_key, the connection test bailed early with "URL and API key required". Fix: 16 new persist branches inupdate_encoding_settings(8 jellyfin + 8 emby), with****masking-roundtrip guards on the api_key fields. Addedtest_jellyfin_settings_round_tripandtest_emby_settings_round_tripto lock the behavior in.
Docker images
Pinned to this release:
docker pull ghcr.io/i-ial9000/shrinkerr:0.4.2 # portable (amd64 + arm64, CPU)
docker pull ghcr.io/i-ial9000/shrinkerr:0.4.2-nvenc # x86_64 + NVIDIA GPU (NVENC)
docker pull ghcr.io/i-ial9000/shrinkerr:0.4.2-edge # as above but ffmpeg master
docker pull ghcr.io/i-ial9000/shrinkerr:0.4.2-edge-nvencFloating tags (:latest, :edge, :nvenc, :edge-nvenc) track the most recent release of each lineage.