Lidarr 3.1.6.5079 upgrade: no breaking changes, clean test

released
lab run
upgraded from
3.1.0.4875
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

3.1.6.5079 is the stable release that rolls up the 3.1.1 to 3.1.6 builds, which were published as prereleases. The release notes are a plain commit list. Main items, as reported there:

  • Host settings: new “Trusted Networks” setting, hostname validation, a health check that no longer skips when Allowed Hosts is *, and better logging for both settings.
  • qBittorrent: API key support, a login fix for qBittorrent 5.2, a basic auth fix, and cookie reuse.
  • New: plugin support, a Postgres connection string option, a “Custom Format: Format Name” rename token.
  • Fixes: single-file import from Freebox, release group set on manual import, empty mediums after refreshing an album, artist images not downloading, backup download with a trailing slash, Discord timestamp format.
  • Runtime: .NET 8.0.27, SQLite 3.53.4, bulk updates wrapped in a transaction.

Breaking changes and deprecations

The release notes list no breaking changes. If you run Docker, they say to pull the new image and not update Lidarr inside an existing container.

Tested in our lab

  • Installed 3.1.0.4875 (the linuxserver/lidarr image) with Docker Compose, created a tag through the API, and confirmed the API answered.
  • Stopped the stack with docker compose down, changed the image tag to 3.1.6.5079, pulled and started it.
  • After the upgrade the version reported 3.1.6.5079, the web UI returned HTTP 200, the API key was unchanged, and the tag was still there.
  • Health checks showed only the usual “no indexers” and “no download client” messages from an empty install. The “new update available” warning was gone.
  • No lines containing error, warn or fatal in the container log after the upgrade.
  • The new allowedHosts and trustedNetworks settings appear in the host config, empty by default.

Not tested: real indexers, download clients (including qBittorrent), plugins, Postgres, importing music, and the Allowed Hosts and Trusted Networks behaviour. The lab used an empty library and the default SQLite database.

Lab log

$ docker compose up -d
$ curl -s localhost:8686/initialize.json
  "version": "3.1.0.4875",
$ curl -s -X POST -H "X-Api-Key: [redacted]" -H "Content-Type: application/json" -d "{\"label\":\"labtag\"}" localhost:8686/api/v1/tag
{
  "label": "labtag",
  "id": 1
}
$ docker compose down
 Container lidarr Removed 
$ sed -i "s/3.1.0.4875-ls45/3.1.6.5079-ls46/" compose.yaml
$ docker compose pull
 Image lscr.io/linuxserver/lidarr:3.1.6.5079-ls46 Pulled 
$ docker compose up -d
 Container lidarr Started 
$ curl -s localhost:8686/initialize.json | grep -E "version|apiKey"
  "apiKey": "[redacted]",
  "version": "3.1.6.5079",
$ curl -s -H "X-Api-Key: [redacted]" localhost:8686/api/v1/tag
[
  {
    "label": "labtag",
    "id": 1
  }
]
$ curl -s -o /dev/null -w "%{http_code}\n" localhost:8686/
200
$ docker ps --format "{{.Names}} {{.Status}}"
lidarr Up 48 seconds

Reported by others

We did not review issue trackers or forums for this release. Everything under Summary comes from the official release notes.

Verdict

Upgrade now. In our lab the upgrade from 3.1.0 was clean, and the release adds fixes and host-security options. Back up your /config folder first, as always. If you use qBittorrent, re-run the connection test after upgrading.

sources