lidarr-plugins: 3.1.1.4884 -> 3.1.1.4901

[github-actions]

This PR was created automatically by the Update Packages workflow.

[mergify]

Merge Queue Status

Rule: default

---

• ✅ Entered queue — 2026-01-17 17:26 UTC
• ✅ Checks started · on draft merge queue: embarking master (7bac694) and #477 together #478
• 🚫 Left the queue — 2026-01-17 17:26 UTC · at 44b645f540da395b69e8fd40c760e7d01b866485

This pull request spent 8 seconds in the queue, including 1 second running CI.

Required conditions to merge

• #approved-reviews-by>=1
  • lidarr-plugins: 3.1.1.4884 -> 3.1.1.4901 #477
• #check-failure==0
• #commits-behind <= 10
  • lidarr-plugins: 3.1.1.4884 -> 3.1.1.4901 #477
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • lidarr-plugins: 3.1.1.4884 -> 3.1.1.4901 #477

Reason

Pull request #477 has been dequeued, merge conditions unmatch:

• #approved-reviews-by>=1
• #check-failure==0
• #commits-behind <= 10
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 Enforce conventional commit

This rule is failing.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🔴 Do not merge outdated PRs

This rule is failing.

Make sure PRs are almost up to date before merging

• #commits-behind <= 10