This release contains fixes for issues resulting from backward-incompatible changes to the Prowlarr API.
- Add the
sync_reject_blocklisted_torrent_hashesattribute to the Lidarr, Radarr, Readarr, Sonarr and Whisparr application definitions (available in Prowlarr v1.15 and above). - Add the
always,preferredandneveroptions to theuse_encryptionattribute on email notification connections.- In version 0.5.2 and below of the plugin,
trueandfalsevalues were used when defining this attribute. In older versions of Prowlarr, these values used to correspond toalwaysandpreferred, respectively.trueandfalsecan still be used, but in newer versions of Prowlarr,falsenow corresponds tonever. neveris available in Prowlarr v1.13 and above. Ifneveris selected on an older version, it will result inpreferredbeing used.
- In version 0.5.2 and below of the plugin,
- Make sure the Prowlarr plugin does not raise an error when new (unimplemented) resource attributes are found, and instead ensure they are passed through without modification. This ensures that backwards-compatible API additions do not cause any problems when using Buildarr with newer versions of Prowlarr.
In addition, the following issues were resolved:
- Loosen Pushover user/API key constraints, to allow Pushover notification connections to be managed following the change to Prowlarr to obfuscate secret values in API responses.
Changed
- Fix compatibility with newer versions of Prowlarr (#66)