Skip to main content

Upgradinatorr

Automated media upgrade search for Starr applications (Radarr, Sonarr, Lidarr, Readarr).

Installation

uv tool install upgradinatorr

Or install from source:

git clone https://github.com/yourusername/upgradinatorr
cd upgradinatorr
uv sync
source .venv/bin/activate  # or prefix the commands below with `uv run`

Usage

# Process single application
upgradinatorr -a radarr

# Process multiple applications
upgradinatorr -a radarr,sonarr

# Process multiple instances
upgradinatorr -a radarr,radarr4k

# Use custom config file
upgradinatorr -a radarr -c /path/to/config.conf

# Enable verbose output
upgradinatorr -a radarr --verbose

# Preview processing
upgradinatorr -a radarr --dry-run

Docker Usage

Run with docker:

docker run --rm \
  -e PUID=99 \
  -e PGID=100 \
  -v /mnt/user/appdata/upgradinatorr/config:/config \
  mountaingod2/upgradinatorr:latest \
  -a radarr,sonarr --verbose

Or use docker-compose:

name: upgradinatorr

services:
  upgradinatorr:
    image: mountaingod2/upgradinatorr:latest
    container_name: upgradinatorr
    volumes:
      - /path/to/config:/config
    environment:
      - PUID=99
      - PGID=100
    command: ["-a", "radarr,sonarr", "--verbose"]

Environment Variables:

[!TIP] Run id to display values for the current user.

  • PUID - User ID to run as (default: 999)
  • PGID - Group ID to run as (default: 999)

Volumes:

  • /config - Directory containing your upgradinatorr.conf file

The container will automatically create a default config file from the example if one doesn't exist.

Configuration

App arguments passed to -a/--apps should match your config section names (case-insensitive). For example, if your config has [Radarr] and [Radarr4K], use -a radarr,radarr4k.

Create a upgradinatorr.conf file (see example from original repo):

[Notifications]
DiscordWebhook=https://discord.com/api/webhooks/...
NotifiarrPassthroughWebhook=https://notifiarr.com/api/v1/notification/passthrough/...
NotifiarrPassthroughDiscordChannelId=123456789

[Radarr]
ApiKey=your_api_key_here
Count=10
Monitored=true
MovieStatus=released
TagName=upgrade
Unattended=false
Url=http://localhost:7878

[Sonarr]
ApiKey=your_api_key_here
Count=5
Monitored=true
SeriesStatus=continuing
TagName=upgrade
Unattended=false
Url=http://localhost:8989

Requirements

  • Python 3.12+
  • aiohttp
  • stamina
  • rich
  • rich-click
  • pydantic

License

MIT

Credits

Original PowerShell version by angrycuban13

Metadata

Release files for upgradinatorr 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for upgradinatorr 0.2.1
File Size Uploaded
upgradinatorr-0.2.1.tar.gz 20.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for upgradinatorr 0.2.1
File Interpreter ABI Platform
upgradinatorr-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 46.7 kB

Release files / upgradinatorr-0.2.1.tar.gz

Download URL upgradinatorr-0.2.1.tar.gz
Size 20.4 kB
Tags Source
SHA-256 checksum
How to use checksums
7d530cbb8db34cd1b0964f1e31633a76e2450dd8c6177717fc0f9d079e285426
BLAKE2b-256 checksum
How to use checksums
7dbfa999b01976c978a5397a079597ab26eedf77d68b6a9820aba19f7a863f5f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.

Transparency log

Release files / upgradinatorr-0.2.1-py3-none-any.whl

Download URL upgradinatorr-0.2.1-py3-none-any.whl
Size 26.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ade5f1bc9017ffd5b370006355af1197aac2f322f27e449531114d62d6633303
BLAKE2b-256 checksum
How to use checksums
520c5e1b7a7605d6e4c36d9836b07f4687a45a20e49030d49ea8b9d7434d2086
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.7

2 release files

0.3.6

2 release files

0.3.5

2 release files

0.3.4

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.2.2

2 release files

This release

0.2.1 This release

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page