fix(container): update image ghcr.io/searxng/searxng (2026.7.26-b060c780d ➔ 2026.7.28-8372f5d85)

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/searxng/searxng (source)	patch	2026.7.26-b060c780d → 2026.7.28-8372f5d85

---

Configuration

📅 Schedule: (in timezone Europe/Brussels)

• 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 these updates again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

• Chores
  • Updated SearXNG to a newer release, providing the latest available fixes and improvements.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3812ad23-ff38-4844-b57d-f3395fc3a9e6

📥 Commits

Reviewing files that changed from the base of the PR and between c903a17 and e2d66ee.

📒 Files selected for processing (1)

• kubernetes/apps/default/searxng/app/helmrelease.yaml

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• Tanguille/LLMKube (auto-detected)
• Tanguille/2x-R9700-RDNA4-GFX1201-sglang-inference (auto-detected)

---

📝 Walkthrough

Walkthrough

The SearXNG HelmRelease now references a newer pinned container image tag and digest. No other deployment configuration changed.

Changes

SearXNG image update

Layer / File(s)	Summary
Update pinned SearXNG image kubernetes/apps/default/searxng/app/helmrelease.yaml	The SearXNG container image reference was updated to the newer version and SHA256 digest.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• Tanguille/cluster#4175: Updates the same SearXNG image reference in the same HelmRelease.
• Tanguille/cluster#4184: Changes the SearXNG HelmRelease image tag and digest.
• Tanguille/cluster#4188: Updates a HelmRelease-managed container image tag and digest.

Suggested reviewers: tanguille

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately summarizes the main change: updating the SearXNG container image to a newer version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/ghcr.io-searxng-searxng-2026.x

---

_{Comment @coderabbitai help to get the list of available commands.}

[tanguille-cluster]

@@ spec.template.spec.containers.app.image @@
# apps/v1/Deployment/default/searxng
! ± value change
- ghcr.io/searxng/searxng:2026.7.26-b060c780d@sha256:d0aaeb14880e6e92bde1518fcc7261e995783367d63d95203383607bef9c6516
+ ghcr.io/searxng/searxng:2026.7.28-8372f5d85@sha256:5dd626fecd8127857437b3ba11d9e8d8380dd74d8b3773129ccf68b839eadb85

[tanguille-cluster]

@@ spec.values.controllers.app.containers.app.image.tag @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/default/searxng
! ± value change
- 2026.7.26-b060c780d@sha256:d0aaeb14880e6e92bde1518fcc7261e995783367d63d95203383607bef9c6516
+ 2026.7.28-8372f5d85@sha256:5dd626fecd8127857437b3ba11d9e8d8380dd74d8b3773129ccf68b839eadb85

[github-actions]

AI Automated Review

Analysis engine: qwen-3.6-fast@http://litellm.ai.svc.cluster.local/v1 (openai)

Recommendation: Approve

This is a straightforward container image digest update for SearXNG from 2026.7.26-b060c780d to 2026.7.28-8372f5d85. The change is minimal, focused, and follows repository conventions.

Change-by-change findings

kubernetes/apps/default/searxng/app/helmrelease.yaml

• Updated image tag from 2026.7.26-b060c780d@sha256:d0aaeb14880e6e92bde1518fcc7261e995783367d63d95203383607bef9c6516 to 2026.7.28-8372f5d85@sha256:5dd626fecd8127857437b3ba11d9e8d8380dd74d8b3773129ccf68b839eadb85.
• This is a patch-level bump (same major.minor date-based version scheme) with an updated commit hash and digest. No other manifest fields changed.

Standards Compliance

• ✅ Uses Conventional Commit title (fix(container): ...).
• ✅ Only one file changed, keeping the PR focused.
• ✅ Image includes a SHA256 digest for supply-chain safety.
• ✅ No secrets, credentials, or sensitive data exposed.
• ✅ Manifest structure follows existing patterns (app-template chart, Flux HelmRelease).

Must-Check Items

1. Validate manifest against target cluster version: The manifest uses helm.toolkit.fluxcd.io/v2 API, which is compatible with current Flux versions. No schema violations detected; the YAML aligns with the referenced app-template chart schema. No changes to resource requests/limits, security context, probes, or persistence were made, so no cluster-version incompatibility risk is introduced by this bump.

2. Check for resource quota / limit changes: No resource changes. CPU/memory requests (50m/256Mi) and limits (500m/1Gi) remain unchanged. No new resources added.

Unknowns / Needs Verification

• Upstream release notes for SearXNG 2026.7.28-8372f5d85 were not available via the GitHub Releases API (empty response). The tag format suggests a daily/dev build rather than a formal release. Without upstream changelog evidence, I cannot confirm whether this contains bug fixes, features, or breaking changes. However, given the minor nature of the bump (two-day delta in the date-stamped version) and the fact that Renovate classifies it as a patch, the risk is low. If operational issues arise after merge, check SearXNG upstream for any regressions between these commits.