Skip to content
Open
Show file tree
Hide file tree
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
8 changes: 4 additions & 4 deletions .github/workflows/pre-commit.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,23 +19,23 @@ jobs:

steps:
- name: 📥 Checkout repository
uses: actions/checkout@v5
uses: actions/checkout@v7
with:
fetch-depth: 0

- name: 🐍 Setup Python 3.11
uses: actions/setup-python@v6
uses: actions/setup-python@v7
with:
python-version: "3.11"
cache: "pip"

- name: 📦 Setup Node.js 20
uses: actions/setup-node@v5
uses: actions/setup-node@v7
with:
node-version: "20"

- name: 🔧 Cache pre-commit environments
uses: actions/cache@v4
uses: actions/cache@v6
with:
path: |
~/.cache/pre-commit
Expand Down
8 changes: 4 additions & 4 deletions .github/workflows/prowlarr-ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -18,24 +18,24 @@ jobs:
env:
API_KEY: fakeapikey
steps:
- uses: actions/checkout@v5
- uses: actions/checkout@v7

- name: Setup Python
uses: actions/setup-python@v6
uses: actions/setup-python@v7
with:
python-version: "3.10"
cache: "pip"

- name: Setup Node.js
uses: actions/setup-node@v5
uses: actions/setup-node@v7
with:
node-version: "18"

- name: Install Python dependencies
run: pip install -r requirements.txt

- name: Cache pre-commit hooks
uses: actions/cache@v4
uses: actions/cache@v6
with:
path: ~/.cache/pre-commit
key: pre-commit-${{ hashFiles('.pre-commit-config.yaml') }}
Expand Down
7 changes: 0 additions & 7 deletions lidarr/settings.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,6 @@ Click **Add (+)** to add a root folder. The path must exist and Lidarr must have
> Don't point a root folder at a cloud storage mount (Dropbox, OneDrive, Google Drive). Lidarr writes audio tags and metadata frequently; cloud storage APIs have rate limits that will cause failures.
{.is-warning}


## Metadata Profiles

{#metadata-profiles}
Expand Down Expand Up @@ -158,7 +157,6 @@ You can include or exclude secondary types (Compilation, Soundtrack, Spokenword,
> MusicBrainz determines release types. If a release you expect to see is missing, check its entry on MusicBrainz: the type may be `Unknown`, which Lidarr can't filter on, or the primary type may be one you have unchecked in your profile.
{.is-info}


## Release Profiles

{#release-profiles}
Expand All @@ -179,7 +177,6 @@ Release profiles filter and score releases based on their titles. Use them to re
> Release profiles apply at **grab/download time**: they filter and score releases from indexers before Lidarr sends anything to a download client. They have no effect on which MusicBrainz release (pressing, edition, format) Lidarr matches your already-downloaded files to during import. See [FAQ → Can Lidarr prefer a specific pressing or format during import?](/lidarr/faq#can-lidarr-prefer-a-specific-pressing-or-format-during-import) for the import side of this.
{.is-info}


## Custom Formats

{#custom-formats-2}
Expand Down Expand Up @@ -214,7 +211,6 @@ Two ways to test how Lidarr will parse a release name before committing to a pro

**Via the Servarr Discord bot:** In the `#bot-spam` channel, run `/parser lidarr <release title>` (for example, `/parser lidarr Artist.Album.2022.FLAC-GROUP`). The bot replies with the same parsed breakdown. Useful for quick spot-checks without opening the UI.


# Quality

{#quality}
Expand All @@ -233,7 +229,6 @@ For audio, size limits use **kilobits per second (kbps)**. Lidarr computes a bit
> FLAC is lossless and doesn't have a consistent bitrate; its effective bitrate varies by content. The FLAC entry in quality definitions serves primarily as a file-size sanity check rather than strict bitrate enforcement.
{.is-info}


# Download Clients

{#download-clients}
Expand Down Expand Up @@ -341,7 +336,6 @@ A mapping translates a remote path (as reported by the download client) to a loc
> If both Lidarr and the download client are in Docker containers on the same host with matching volume mounts, a remote path mapping isn't needed. See [TRaSH's Remote Path Mapping guide](https://trash-guides.info/Radarr/Radarr-remote-path-mapping/) for diagnosis and setup.
{.is-info}


# Connect

{#connections}
Expand Down Expand Up @@ -371,7 +365,6 @@ Click **Add (+)** and select a connection type. Most connections share these fie

For **Custom Script** connections, see the [Custom Scripts](/lidarr/custom-scripts) page for the full list of environment variables available per event.


# Tags

{#tags}
Expand Down
2 changes: 1 addition & 1 deletion lidarr/tips-and-tricks.md
Original file line number Diff line number Diff line change
Expand Up @@ -421,4 +421,4 @@ As long as the root folder paths in the backup are still valid on the destinatio
- [Metadata Troubleshooting](/lidarr/metadata-troubleshooting) — when MusicBrainz data is missing or stale
- [Import Troubleshooting](/lidarr/import-troubleshooting) — when downloads finish but don't import
- [Troubleshooting](/lidarr/troubleshooting) — general runtime issues
- [TRaSH Guides](https://trash-guides.info/) — community recipes for media server setups
- [TRaSH Guides](https://trash-guides.info/) — community recipes for media server setups
Loading