feat(container)!: Update image ghcr.io/recyclarr/recyclarr ( 6.0.2 → 7.1.1 )
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| ghcr.io/recyclarr/recyclarr | major | 6.0.2 -> 7.1.1 |
Release Notes
recyclarr/recyclarr (ghcr.io/recyclarr/recyclarr)
v7.1.1
Changed
- The
--app-dataoption is now common to all commands.
Fixed
- CLI: Commands no longer crash due to a null app data directory variable (#288).
v7.1.0
Added
- Sync: In rare circumstances outside of Recyclarr, quality profiles become invalid due to missing required qualities. When this happens, users are not even able to save the profile using the Sonarr or Radarr UI. Recyclarr now detects this situation and automatically repairs the quality profile by re-adding these missing qualities for users. See this issue.
Fixed
- CLI: Signal interrupt support for all API calls. Now when you press CTRL+C to gracefully exit/cancel Recyclarr, it will bail out of any ongoing API calls.
- CLI: The
--app-dataoption works again (#284).
v7.0.0
This release contains BREAKING CHANGES. See the v7.0 Upgrade Guide for required changes you may need to make.
Added
- YAML: New
includessubdirectory intended to hold only include templates. Relative paths specified in theconfiginclude directive are resolved starting at this new directory. Relative paths to include templates located under theconfigsdirectory is now DEPRECATED. See the "File Structure" page on the wiki for more details. - Support the NO_COLOR environment variable for all Recyclarr commands (#223).
Changed
- BREAKING: The app data directory on OSX has changed. It now lives at
~/Library/Application Support/recyclarrinstead of~/.config/recyclarr. Users will need to runrecyclarr migrateto move the directory (or do it manually). - BREAKING: Removed support for Release Profiles and Sonarr version 3. The new minimum required version for Sonarr is v4.0.0.
- CLI: Slightly improved display of version number when using
-voption. - CLI: Greatly improved the layout of and information in the local starter YAML configuration that
Recyclarr generates with the
recyclarr config createcommand.
Fixed
- YAML: Print more useful diagnostics when there's a connectivity problem to a service (e.g.
incorrect
base_url). - YAML: Regression that prevented basic validation of
base_url&api_key. - CLI: CFs with no Trash ID will no longer be displayed when running the
list custom-formatscommand (#229). - Docker: Support running the container in read-only mode (#231).
- Sync: Sometimes CFs weren't deleted even with
delete_old_custom_formatsenabled (#237).
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.
--- k8s/nebula/apps/media/recyclarr/app Kustomization: flux-system/recyclarr HelmRelease: media/recyclarr
+++ k8s/nebula/apps/media/recyclarr/app Kustomization: flux-system/recyclarr HelmRelease: media/recyclarr
@@ -40,13 +40,13 @@
TZ: Europe/Helsinki
envFrom:
- secretRef:
name: recyclarr
image:
repository: ghcr.io/recyclarr/recyclarr
- tag: 6.0.2
+ tag: 7.1.1
probes:
liveness:
enabled: true
readiness:
enabled: true
resources:
--- HelmRelease: media/recyclarr Deployment: media/recyclarr
+++ HelmRelease: media/recyclarr Deployment: media/recyclarr
@@ -41,13 +41,13 @@
- env:
- name: TZ
value: Europe/Helsinki
envFrom:
- secretRef:
name: recyclarr
- image: ghcr.io/recyclarr/recyclarr:6.0.2
+ image: ghcr.io/recyclarr/recyclarr:7.1.1
name: app
resources:
limits:
memory: 200Mi
requests:
cpu: 10m
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.