Prowlarr 3.0.2.5780 upgrade: .NET 10, Postgres 15+, clean in Docker

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

Summary

This is the first stable release of the 3.0 line. It rolls up the 3.0.0, 3.0.1 and 3.0.2 changes, which were only prereleases. The big change is the move to .NET 10. There are also a few fixes: API keys in JSON-escaped query strings are now removed from logs, a rejected grab is reported when qBittorrent already has the release, and a login redirect bug with forms authentication is fixed. Anthelion is added as a default torznab preset.

Breaking changes and deprecations

Reported in the release notes (not all tested by us):

  • The minimum Postgres version is now 15 (“New: Bump minimum Postgres version to 15 for FluentMigrator”). If you use an external Postgres database, check its version before you upgrade. We did not test Postgres.
  • .NET moves to 10 (“New: Bump .NET to 10”). Docker users get this with the new image. Non-Docker users should check the platform requirements.
  • “New: Removed Special Handling of Reflinks for BTRFS and ZFS”, and ZFS reflink support was added in the same range.
  • Non-Docker installs must switch the update branch to master to keep getting updates. Docker users must pull a new image and must not update inside the container.

Tested in our lab

We upgraded a Docker install with the default SQLite database from 2.7.0.5723 (the previous stable) to 3.0.2.5780, using the linuxserver.io image.

  • Version 2.7.0 started, answered /ping and reported the .NET 8 runtime.
  • We created a tag through the API, then stopped the container with docker compose down, changed the image tag, pulled, and started it again.
  • After the upgrade, the API reported 3.0.2.5780 on .NET 10.0.15. /ping returned 200, and the tag was still there.
  • The container log showed no lines matching error, warn, fatal or exception.
  • The health check showed only “No indexers enabled”. That is expected, because we added no indexers.

Not tested: Postgres, non-Docker installs, real indexers, and download client or app (Sonarr/Radarr) sync.

Lab log

$ curl -s -H "X-Api-Key: [redacted]" localhost:9696/api/v1/system/status | grep -E "\"(version|databaseType|runtimeVersion)\""
  "version": "2.7.0.5723",
  "databaseType": "sqLite",
  "runtimeVersion": "8.0.27",
$ curl -s -X POST -H "X-Api-Key: [redacted]" -H "Content-Type: application/json" -d "{\"label\":\"labtest\"}" localhost:9696/api/v1/tag
{
  "label": "labtest",
  "id": 1
}
$ docker compose down
[...]
 Network prowlarr_default  Removed
$ sed -i "s/prowlarr:2.7.0/prowlarr:3.0.2/" compose.yaml
$ docker compose pull
[...]
 prowlarr Pulled
$ docker compose up -d
 Container prowlarr  Starting
 Container prowlarr  Started
$ curl -s -H "X-Api-Key: [redacted]" localhost:9696/api/v1/system/status | grep -E "\"(version|databaseType|runtimeVersion)\""
  "version": "3.0.2.5780",
  "databaseType": "sqLite",
  "runtimeVersion": "10.0.15",
$ curl -s -o /dev/null -w "%{http_code}\n" localhost:9696/ping
200
$ curl -s -H "X-Api-Key: [redacted]" localhost:9696/api/v1/tag
[
  {
    "label": "labtest",
    "id": 1
  }
]
$ docker logs prowlarr 2>&1 | grep -iE "error|warn|fatal|exception" | head

Reported by others

Only the release notes were used. We did not review issue reports for this release.

Verdict

Upgrade now if you run Prowlarr on SQLite in Docker: our upgrade was clean. If you use Postgres, confirm it is version 15 or newer first. Back up your config folder before you upgrade, as always.

sources

other Prowlarr releases