Buildarr-prowlarr

This release contains fixes for issues resulting from backward-incompatible changes to the Prowlarr API.

* Add the `sync_reject_blocklisted_torrent_hashes` attribute to the Lidarr, Radarr, Readarr, Sonarr and Whisparr application definitions (available in Prowlarr v1.15 and above).
* Add the `always`, `preferred` and `never` options to the `use_encryption` attribute on email notification connections.
* In version 0.5.2 and below of the plugin, `true` and `false` values were used when defining this attribute. In older versions of Prowlarr, these values used to correspond to `always` and `preferred`, respectively. `true` and `false` can still be used, but in newer versions of Prowlarr, `false` now corresponds to `never`.
* `never` is available in Prowlarr v1.13 and above. If `never` is selected on an older version, it will result in `preferred` being used.
* 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](https://github.com/buildarr/buildarr-prowlarr/pull/66))

This release contains mitigations for an issue where on newer versions of Prowlarr, secret values are obfuscated in API responses to avoid exposing them on insecure applications.

In the best case scenario, they cause Buildarr to always re-apply the configuration for a resource, as they always report as "changed". In the worst case scenario, the obfuscated values violate strict value constraints set in Buildarr, causing errors to occur when fetching remote instance configurations.

The fixes in this release resolve this worst case scenario.

A more permanent fix for handling this problem in general is planned for future releases of Buildarr.

Changed

* Loosen secret value constraints ([61](https://github.com/buildarr/buildarr-prowlarr/pull/61))

This release adds the following new features:

* Support defining a URL base for the Prowlarr instance in the Buildarr configuration, using the `url_base` host configuration attribute.
* This allows Prowlarr instances with APIs available under a custom path (e.g. `http://localhost:9696/prowlarr`) to be managed by Buildarr.
* Add support for auto-fetching the Prowlarr API key when dumping instance configurations, by pressing the Enter key without specifying an API key when prompted.
* This brings the Prowlarr plugin in line with other Buildarr plugins which already support this.
* Add support for auto-fetching the Prowlarr API key from newer versions of Prowlarr which use the `initialize.json` endpoint.

The following issues have also been fixed:

* Use the Buildarr-global API request timeout setting as the timeout for Prowlarr API requests, instead of not using a timeout.

Changed

* Add Prowlarr instance URL base support ([54](https://github.com/buildarr/buildarr-prowlarr/pull/54))

This updates the Prowlarr plugin so that it is compatible with [Buildarr v0.7.0](https://buildarr.github.io/release-notes/#v070-2023-11-12).

Changed

* Add Buildarr v0.7.0 support ([48](https://github.com/buildarr/buildarr-prowlarr/pull/48))

This release fixes the following issues:

* Fix a username/password related parsing error when the authentication method is not explicitly defined in the Buildarr configuration

Changed

* Remove validation for username/password ([44](https://github.com/buildarr/buildarr-prowlarr/pull/44))

This release adds support for the `external` authentication method for Prowlarr, and makes it possible for Buildarr to manage Prowlarr instances configured to use the `external` authentication method.

This authentication method is usually only accessible by manually modifying the Prowlarr configuration file, but Buildarr makes it possible to configure it automatically.

The following issues have also been fixed:

* Fix a regression in the previous release where new application definitions could not be created
* Remove support for the `none` authentication method, no longer usable in Prowlarr v1.0 and later

Added

* Add support for external authentication ([37](https://github.com/buildarr/buildarr-prowlarr/pull/37))

Changed

* FIx creating application definitions ([39](https://github.com/buildarr/buildarr-prowlarr/pull/39))
* Fix Sonarr/Radarr plugin links in docs ([40](https://github.com/buildarr/buildarr-prowlarr/pull/40))

Removed

* Remove support for no authentication ([38](https://github.com/buildarr/buildarr-prowlarr/pull/38))