Skip to content

fix(container): update image ghcr.io/home-operations/sonarr ( 5.0.0.2838 ➔ 5.0.0.2870 ) - #2136

Open
mortyops[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-home-operations-sonarr-5.x
Open

mortyops[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-home-operations-sonarr-5.x

Conversation

@mortyops

@mortyops mortyops Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/home-operations/sonarr (source) patch 5.0.0.2838 → 5.0.0.2870

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

Sonarr/Sonarr (ghcr.io/home-operations/sonarr)

v5.0.0.2870: 5.0.0.2870

Compare Source

What's Changed
Changes
New Contributors

Full Changelog: Sonarr/Sonarr@v5.0.0.2838...v5.0.0.2870


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

…838 ➔ 5.0.0.2870 )

| datasource | package                        | from       | to         |
| ---------- | ------------------------------ | ---------- | ---------- |
| docker     | ghcr.io/home-operations/sonarr | 5.0.0.2838 | 5.0.0.2870 |
@mortyops

mortyops Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor Author
--- Deployment downloads/sonarr
+++ Deployment downloads/sonarr
@@ -51,7 +51,7 @@
         envFrom:
         - secretRef:
             name: sonarr-secret
-        image: ghcr.io/home-operations/sonarr:5.0.0.2838
+        image: ghcr.io/home-operations/sonarr:5.0.0.2870
         livenessProbe:
           failureThreshold: 3
           httpGet:

@mortyops

mortyops Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor Author
--- HelmRelease downloads/sonarr
+++ HelmRelease downloads/sonarr
@@ -52,7 +52,7 @@
                 name: sonarr-secret
             image:
               repository: ghcr.io/home-operations/sonarr
-              tag: 5.0.0.2838
+              tag: 5.0.0.2870
             probes:
               liveness:
                 custom: true

@github-actions

Copy link
Copy Markdown

✅ Automated recommendation: APPROVE

Analysis engine: pr-review-local (openai) · pr-reviewer-action v3.7.0

Recommendation

Approve. This is a single-line patch bump of ghcr.io/home-operations/sonarr from 5.0.0.2838 to 5.0.0.2870. The change is a pure image tag update with no other manifest edits, no new resources, no secrets, and no structural changes.

Change-by-Change Findings

kubernetes/apps/base/downloads/sonarr/app/helmrelease.yaml (line 42)

  • Image tag bump: 5.0.0.2838 → 5.0.0.2870. This is a patch-level update within the 5.0.0.x series. The release notes (from the PR body) list only translations, TMDb import lists, multi-season pack support, calendar improvements, log message cleansing, series search refactor, queue action button context, release name display, Norwegian translation fixes, GitHub Actions bump, and a missing episode-file-details fix — none of which are breaking or require manifest changes.
  • No other diff lines: The diff is exactly one line changed. No new env vars, no new probes, no new resources, no new annotations.

Required Checks Disposition

Check Status Rationale
validate manifest against target cluster version satisfied The manifest uses helm.toolkit.fluxcd.io/v2 (standard HelmRelease API) and OCIRepository chartRef — both are stable APIs present on the target cluster. No deprecated or removed fields are introduced. The schema comment at line 1 ($schema=.../app-template/schemas/helmrelease-helm-v2.schema.json) is valid.
check for resource quota / limit changes satisfied No resources.requests or resources.limits lines are changed. The existing limits (cpu: 20m, memory: 384Mi / memory: 2Gi) are untouched.

Standards Compliance

  • No plaintext secrets: The diff contains no secrets. The sonarr-secret is referenced via secretRef (ExternalSecret/1Password pattern). ✓
  • No postRenderer with bash: Not present. ✓
  • No secrets under **/resources/**: Not applicable — no resources/ path changed. ✓
  • Flux schema comment: Present at line 1 with a valid kubernetes-schemas.pages.dev URL. ✓
  • Naming convention: helmrelease.yaml is lowercase kebab-case. ✓
  • No ${...} literal substitution risk: No ${...} tokens in the diff. ✓
  • healthChecks: targets rendered workload: The manifest does not define healthChecks: on the HelmRelease itself (it relies on the app-template's default health checks on the Deployment). This is acceptable — the standard says "never the HelmRelease" and the rendered Deployment is the signal. ✓
  • wait: not set to true: Not present (defaults to false). ✓
  • No CiliumClusterwideNetworkPolicy changes: Not applicable. ✓
  • No security.cephx.csi changes: Not applicable. ✓
  • No rgw_sigv4_insecure changes: Not applicable. ✓

Unknowns / Needs Verification

  • Image digest verification: The diff does not include a @sha256: digest for the new tag. The previous tag 5.0.0.2838 also lacked a digest. This is a minor hygiene gap — adding a digest would make the image immutable. However, since the tag is pinned to a specific version and the image is from a private registry (ghcr.io/home-operations/sonarr), the risk of tag replay is low. Not a blocker.
  • Flux flate vs strict substitution: No ${...} tokens are introduced, so the strict envsubst freeze risk is not triggered. ✓

Summary

This is a low-risk, single-line patch bump. The release notes confirm non-breaking changes. No manifest structure is altered. No secrets, no networking, no storage, no GPU changes. Approved for merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants