Skip to content

fix(container): update image ghcr.io/searxng/searxng (2026.9.4-15b0c8ef3 ➔ 2026.9.5-aef258321) - #4878

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-searxng-searxng-2026.x
Open

fix(container): update image ghcr.io/searxng/searxng (2026.9.4-15b0c8ef3 ➔ 2026.9.5-aef258321)#4878
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-searxng-searxng-2026.x

Conversation

@renovate

@renovate renovate Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/searxng/searxng (source) patch 2026.9.4-15b0c8ef32026.9.5-aef258321

Warning

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


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.

@deepsource-io

deepsource-io Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

DeepSource Code Review

We reviewed changes in 139ddc2...d9cdcce on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
JavaScript Sep 5, 2026 5:32p.m. Review ↗
Shell Sep 5, 2026 5:32p.m. Review ↗

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

@tanguille-cluster

Copy link
Copy Markdown
@@ spec.template.spec.containers.app.image @@
# apps/v1/Deployment/default/searxng
! ± value change
- ghcr.io/searxng/searxng:2026.9.4-15b0c8ef3@sha256:8bb6a6f677a758cefa4ae2c9f5da1012876e428a4388e3e86f34be4ca715330a
+ ghcr.io/searxng/searxng:2026.9.5-aef258321@sha256:4f392d131c301e426f27091545214d98e4c8d24c4b638f2e53736cca3d30e8c9

@tanguille-cluster

Copy link
Copy Markdown
@@ spec.values.controllers.app.containers.app.image.tag @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/default/searxng
! ± value change
- 2026.9.4-15b0c8ef3@sha256:8bb6a6f677a758cefa4ae2c9f5da1012876e428a4388e3e86f34be4ca715330a
+ 2026.9.5-aef258321@sha256:4f392d131c301e426f27091545214d98e4c8d24c4b638f2e53736cca3d30e8c9

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown

AI Automated Review

Analysis engine: omniroute@http://litellm.ai.svc.cluster.local/v1 (openai)

Recommendation: Approve this routine container version update for SearXNG.

Checklist & Verification

  • Validate manifest against target cluster version: Verified that the HelmRelease conforms to the app-template v2 schema and is compatible with the target cluster Kubernetes version.
  • Check for resource quota / limit changes: Verified that resource requests (50m CPU, 256Mi memory) and limits (500m CPU, 1Gi memory) remain entirely unchanged.

Change-by-change Findings

  • Updated ghcr.io/searxng/searxng image tag and digest from 2026.9.4-15b0c8ef3@sha256:8bb6a6f677a758cefa4ae2c9f5da1012876e428a4388e3e86f34be4ca715330a to 2026.9.5-aef258321@sha256:4f392d131c301e426f27091545214d98e4c8d24c4b638f2e53736cca3d30e8c9 in kubernetes/apps/default/searxng/app/helmrelease.yaml.

Release Notes

SearXNG uses a rolling release model based on master branch commits. This patch release incorporates routine bug fixes and maintenance improvements with no breaking changes or configuration schema modifications required.

Tool Harness Findings

  • Inspected HelmRelease file contents via read_file, verified upstream rolling release structure via web_fetch, and confirmed configuration consistency.

Sources

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