Skip to content

chore(deps): update lscr.io/linuxserver/heimdall docker tag to v2.8.2 - #167

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lscr.io-linuxserver-heimdall-2.x
Open

chore(deps): update lscr.io/linuxserver/heimdall docker tag to v2.8.2#167
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lscr.io-linuxserver-heimdall-2.x

Conversation

@renovate

@renovate renovate Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
lscr.io/linuxserver/heimdall (source) patch 2.8.12.8.2

Configuration

📅 Schedule: (UTC)

  • 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 was generated by Mend Renovate. View the repository job log.

@github-actions

Copy link
Copy Markdown

Helm Template Diff — heimdall

8 changed lines
--- /tmp/old.yaml	2026-08-28 08:03:49.951785615 +0000
+++ /tmp/new.yaml	2026-08-28 08:03:49.398783452 +0000
@@ -27,7 +27,7 @@
     custom.network/heimdall-integrated: egress
     app.kubernetes.io/name: heimdall
     app.kubernetes.io/instance: heimdall
-    app.kubernetes.io/version: "2.8.1"
+    app.kubernetes.io/version: "2.8.2"
     app.kubernetes.io/managed-by: Helm
 spec:
   type: ClusterIP
@@ -51,7 +51,7 @@
     custom.network/heimdall-integrated: egress
     app.kubernetes.io/name: heimdall
     app.kubernetes.io/instance: heimdall
-    app.kubernetes.io/version: "2.8.1"
+    app.kubernetes.io/version: "2.8.2"
     app.kubernetes.io/managed-by: Helm
   name: heimdall
 spec:
@@ -81,7 +81,7 @@
           type: RuntimeDefault
       containers:
         - name: heimdall
-          image: lscr.io/linuxserver/heimdall:2.8.1
+          image: lscr.io/linuxserver/heimdall:2.8.2
           imagePullPolicy: IfNotPresent
           resources:
           securityContext:

lunarys commented Aug 28, 2026

Copy link
Copy Markdown
Owner

Renovate Review: lscr.io/linuxserver/heimdall 2.8.1 → 2.8.2 (patch, heimdall app)

Risk: 🟡 MEDIUM

Check Result
Inputs Incomplete — PR body has no ### Release Notes section, only the summary table (linuxserver/docker-heimdall doesn't appear to publish per-version changelogs Renovate can pull). Falling back to raw version comparison only. Rendered-diff comment (03-apps-apps-heimdall) is present and complete (8 changed lines, no truncation)
Description vs. diff Consistent — table says 2.8.1 → 2.8.2; the only changed file, 03_apps/apps/heimdall/values.yaml, bumps image.tag from 2.8.1 to 2.8.2, nothing else touched
Rendered diff Full, no truncation — cosmetic-only: all 8 changed lines are app.kubernetes.io/version label bumps (Service + Deployment) and the container image: tag string. No resource additions/removals, no RBAC objects present in this diff at all
Changelog vs. config Not assessable — no changelog available to cross-reference against values.yaml (which does set livenessProbe/readinessProbe/podSecurityContextPreset/containerSecurityContextPreset overrides that a breaking change could have intersected, but there's no changelog text to check them against)

Details:

  • The rendered diff itself is the strongest available signal here: identical resource set, only label/tag strings differ — no new env vars, ports, probes, or RBAC changes appeared, which is inconsistent with a breaking change being present in this bump.
  • values.yaml's existing # TODO: access local ca HTTPS endpoints... note is unrelated to this bump — nothing in the (unavailable) changelog can be checked against it, and a linuxserver.io patch release is unlikely to add CA-trust configuration, so no action taken.

Why MEDIUM: The rendered diff itself is fully cosmetic (label/tag-only) and would normally read as Low, but the changelog input is missing entirely for this image, so there's no way to positively rule out an undocumented behavior change beyond what the diff shows — flagged Medium on the missing-input criterion alone, not on any observed defect.


Generated by Claude Code

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant