Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix v0.3.2 release notes #29

Merged
merged 3 commits into from
Mar 2, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions docs/release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,7 @@

This release addresses the following issues:

* Support defining a URL base for the Jellyseerr instance in the Buildarr configuration, using the `url_base` host configuration attribute.
* This allows Jellyseerr instances with APIs available under a custom path (e.g. `http://localhost:5055/jellyseerr`) to be managed by Buildarr.

The following issues have also been fixed:

* Return a more helpful error message when the API key is not specified when dumping Jellyseerr instance configurations.
* Improve error handling when Buildarr was unable to parse a JSON response from the Jellyseerr API.
* Use the global state attribute for API request timeouts available in newer versions of Buildarr, instead of directly reading it from the Buildarr configuration (and using a hard-coded default if not found).
* Fix an issue where in some cases, reading existing Sonarr instance configuration from a Jellyseerr instance can fail if they do not have any anime-relation configuration defined. In particular, if the anime root folder is not defined, the corresponding API field for it might not be found in the Jellyseerr API response, resulting in an error.

### Changed

Expand Down
Loading