Skip to content

chore(deps): update traefik docker tag to v3.7.12 - #169

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/traefik-3.x
Open

chore(deps): update traefik docker tag to v3.7.12#169
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/traefik-3.x

Conversation

@renovate

@renovate renovate Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
traefik (source) patch v3.7.9v3.7.12

Release Notes

traefik/traefik (traefik)

v3.7.12

Compare Source

All Commits

Bug fixes:

Documentation:

v3.7.11

Compare Source

All Commits

Bug fixes:

Documentation:

v3.7.10

Compare Source

All Commits

Bug fixes:

Documentation:

  • [k8s/ingress-nginx] Clarify auth-url/rewrite-target interaction on ingress-nginx provider (#​13607 @​gndz07)

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

No rendered resource changes detected.

lunarys commented Aug 28, 2026

Copy link
Copy Markdown
Owner

Renovate Review: traefik v3.7.9 → v3.7.12 (patch, adguard-home app)

Risk: 🟡 MEDIUM

Check Result
Inputs Changelog complete — full ### Release Notes for v3.7.10, v3.7.11, v3.7.12. Diff comment present (__no_diff__ slug, "No rendered resource changes detected.") but not meaningfully applicable: see Rendered diff row
Description vs. diff Consistent — table says v3.7.9 → v3.7.12; the only changed file, 03_apps/apps/adguard-home/docker/docker-compose.yml, bumps the traefik: service's image: line from traefik:v3.7.9 to traefik:v3.7.12, nothing else touched. Confirmed via repo-wide search that this is an isolated docker-compose Traefik sidecar used only for adguard-home's local reverse proxy — unrelated to the fleet-wide Helm-managed Traefik ingress controller at 02_bootstrap/03_traefik (untouched by this PR, no scope creep)
Rendered diff Structurally not applicableadguard-home is deployed via a raw docker-compose.yml, not a Helm chart, so there is nothing for the "helm template" diff workflow to render for this component. The "No rendered resource changes detected" comment reflects the absence of any Helm-templatable resource, not an actual before/after comparison of the container's behavior. This is a genuine coverage gap for this specific app type (not a workflow defect), so the review relies solely on the changelog and the raw compose-file diff
Changelog vs. config No breaking changes, renamed/removed keys, or config-schema changes across v3.7.10–v3.7.12 — every entry is under "Bug fixes" or "Documentation." Notable fixes: [k8s/ingress-nginx] redirect/TLS-option items are all Kubernetes-Ingress-provider-specific and don't apply here, since this instance uses the static --providers.file.filename=/etc/traefik/config.yml file provider only (per the compose command args), not the Ingress or CRD provider

Details:

  • This Traefik instance only proxies the adguard-home admin UI locally (--entrypoints.web.address=:80, file provider pointing at ./traefik/config.yml); ACME/TLS and the dashboard are commented out in the compose file, so none of the [tls], [acme], or dashboard-related fixes in the changelog are reachable here either.
  • No CRDs, RBAC, or Kubernetes resources of any kind are involved for this container — it's plain Docker Compose, so §4.5/§6.6 don't apply.

Why MEDIUM: The changelog itself shows only inapplicable bug fixes for this deployment (no breaking changes, and the affected areas — k8s providers, ACME/dashboard — aren't in use here), which would normally support Low. It's flagged Medium instead because the rendered-diff mechanism cannot verify anything for a docker-compose-based app — there's no Helm-template ground truth to fall back on if the changelog read turns out to be incomplete, so confidence rests entirely on the changelog text and the 1-line raw diff.


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