fix(container): update image ghcr.io/searxng/searxng (2026.7.25-0909dbc9e ➔ 2026.7.26-b060c780d)

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/searxng/searxng (source)	patch	2026.7.25-0909dbc9e → 2026.7.26-b060c780d

---

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

The SearXNG HelmRelease updates its container image from the 2026.7.25 build to the 2026.7.26 build with a new SHA256 digest.

Changes

SearXNG image update

Layer / File(s)	Summary
Update SearXNG image reference kubernetes/apps/default/searxng/app/helmrelease.yaml	The SearXNG container image tag and SHA256 digest are updated to a newer build.

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

Possibly related PRs

• Tanguille/cluster#4167: Updates a container image tag and digest in a Kubernetes manifest.
• Tanguille/cluster#4175: Updates the SearXNG image tag and SHA256 digest in the same HelmRelease.

Suggested reviewers: tanguille

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the only change: bumping the searxng container image version and digest.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 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.25-0909dbc9e@sha256:3bc6ae0e872ecd4b003e97e9cb58ec0fb56b02d46ad97ea67e2fa4ff2e8ff759
+ ghcr.io/searxng/searxng:2026.7.26-b060c780d@sha256:d0aaeb14880e6e92bde1518fcc7261e995783367d63d95203383607bef9c6516

[tanguille-cluster]

@@ spec.values.controllers.app.containers.app.image.tag @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/default/searxng
! ± value change
- 2026.7.25-0909dbc9e@sha256:3bc6ae0e872ecd4b003e97e9cb58ec0fb56b02d46ad97ea67e2fa4ff2e8ff759
+ 2026.7.26-b060c780d@sha256:d0aaeb14880e6e92bde1518fcc7261e995783367d63d95203383607bef9c6516

[github-actions]

AI Automated Review

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

Recommendation

Approve — routine container image digest update for SearXNG with no manifest, resource, or configuration changes.

Change Summary

• kubernetes/apps/default/searxng/app/helmrelease.yaml: Updated image.tag from 2026.7.25-0909dbc9e@sha256:3bc6ae0... to 2026.7.26-b060c780d@sha256:d0aaeb1....

This is a single-line patch bump of the SearXNG container image, generated by Renovate. No other fields (resources, probes, security context, persistence, routes) are modified.

Must-Check Items

• Validate manifest against target cluster version: The HelmRelease uses apiVersion: helm.toolkit.fluxcd.io/v2, which is stable and compatible with current Flux versions. No schema or API drift detected. ✅
• Check for resource quota / limit changes: Resource requests (cpu: 50m, memory: 256Mi) and limits (cpu: 500m, memory: 1Gi) are unchanged. ✅

Standards Compliance

• Follows repository conventions: uses app-template chart via OCIRepository reference, DRY YAML anchors for ports/probes, envoy-internal parentRef, and standard security context patterns matching peer apps. ✅
• Conventional commit title format used in PR title. ✅
• No secrets, age keys, or SOPS files touched. ✅

Release Notes

No upstream GitHub releases were found for tag 2026.7.26-b060c780d in the searxng/searxng repository. SearXNG uses date-based development tags rather than formal semver releases, so this represents a daily development snapshot bump. No breaking changes or migration steps are expected for this type of incremental update.

Unknowns / Needs Verification

• Upstream release notes for 2026.7.26-b060c780d could not be fetched from GitHub Releases (no matching release tag exists). This is expected for SearXNG's tagging strategy but means user-visible changes between these two snapshots are undocumented. Given the one-day interval and lack of config/manifest changes, risk is assessed as low.