Skip to content

fix(container): update image ghcr.io/searxng/searxng (2026.8.3-0734ee6c7 ➔ 2026.8.5-1689cb1b5) - #4339

Merged
Tanguille merged 1 commit into
mainfrom
renovate/ghcr.io-searxng-searxng-2026.x
Aug 4, 2026
Merged

fix(container): update image ghcr.io/searxng/searxng (2026.8.3-0734ee6c7 ➔ 2026.8.5-1689cb1b5)#4339
Tanguille merged 1 commit into
mainfrom
renovate/ghcr.io-searxng-searxng-2026.x

Conversation

@renovate

@renovate renovate Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/searxng/searxng (source) patch 2026.8.3-0734ee6c72026.8.5-1689cb1b5

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

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Review Change Stack

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: e234477b-ecdd-465f-a76b-2a5d76d01363

📥 Commits

Reviewing files that changed from the base of the PR and between 09da356 and 30d5a8c.

📒 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/toolhive (auto-detected)
  • Tanguille/pr-reviewer-action (auto-detected)
  • Tanguille/renovate-presets (auto-detected)
  • Tanguille/litellm-operator (auto-detected)
  • Tanguille/2x-R9700-RDNA4-GFX1201-sglang-inference (auto-detected)

📝 Walkthrough

Walkthrough

The SearXNG HelmRelease now references image version 2026.8.5-1689cb1b5 with its updated pinned SHA256 digest.

Changes

SearXNG image update

Layer / File(s) Summary
Update image tag and digest
kubernetes/apps/default/searxng/app/helmrelease.yaml
The SearXNG container image reference changed to 2026.8.5-1689cb1b5@sha256:af6bde1....

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

Possibly related PRs

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 concisely identifies the SearXNG container image update and specifies both version changes.
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

Copy link
Copy Markdown
@@ spec.template.spec.containers.app.image @@
# apps/v1/Deployment/default/searxng
! ± value change
- ghcr.io/searxng/searxng:2026.8.3-0734ee6c7@sha256:912f24817104f45556da9f271e073aab9cd19d84647b299a85c232cf1f086e6d
+ ghcr.io/searxng/searxng:2026.8.5-1689cb1b5@sha256:af6bde1e3590f91be5b7c4e393b3bff82ada4b93d60fc10806fe1ed4ba147d4d

@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.8.3-0734ee6c7@sha256:912f24817104f45556da9f271e073aab9cd19d84647b299a85c232cf1f086e6d
+ 2026.8.5-1689cb1b5@sha256:af6bde1e3590f91be5b7c4e393b3bff82ada4b93d60fc10806fe1ed4ba147d4d

@deepsource-io

deepsource-io Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

DeepSource Code Review

We reviewed changes in 09da356...30d5a8c 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 Aug 4, 2026 4:51p.m. Review ↗
Shell Aug 4, 2026 4:51p.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.

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

AI Automated Review

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

Recommendation

Approve. This is a minimal, low-risk Renovate patch bump of the SearXNG container image, pinned by digest. The diff touches a single line in kubernetes/apps/default/searxng/app/helmrelease.yaml and introduces no structural, security, or resource changes.

Change-by-change findings

  • kubernetes/apps/default/searxng/app/helmrelease.yaml — image tag updated from 2026.8.3-0734ee6c7@sha256:912f2481… to 2026.8.5-1689cb1b5@sha256:af6bde1e…. The image remains digest-pinned, consistent with the repository convention of pinning containers to a digest (see commit 9d39a0fa6 fix: automerge containers pinned to a digest). No other values, env, probes, securityContext, persistence, or route fields changed.

Required checks

  • Validate manifest against target cluster version — The change is a single image tag swap. No API versions, chart references, schema fields, or structural elements were modified, so no cluster-version compatibility risk is introduced. The HelmRelease still uses helm.toolkit.fluxcd.io/v2 with the app-template OCIRepository chartRef. I did not run validate-pr.sh / flate against a live cluster in this review (no tool calls were issued), so live rendering was not verified; see Unknowns.
  • Check for resource quota / limit changes — None. The resources block is unchanged (requests: cpu 50m / memory 256Mi, limits: cpu 500m / memory 1Gi). No quota-related fields were touched.

Sources

  • PR metadata and diff (Renovate patch bump, 2026.8.3-0734ee6c72026.8.5-1689cb1b5).
  • Repository history confirms this is a routine Renovate image bump (prior bump 1872aaadd for 2026.8.12026.8.3).
  • GitHub release enrichment for searxng/searxng returned no release tags matching 2026.8.5; upstream release notes were not verified this run.

Standards Compliance

  • Change is small and focused, matching the established Renovate image-bump pattern in this repo.
  • Conventional Commit title used: fix(container): update image ….
  • Digest-pinned image tag follows the repository convention for pinned containers.
  • No shell scripts touched, so the shellcheck requirement does not apply.

Tool Harness Findings

The tool-calling loop issued no tool calls; no evidence was gathered beyond the corpus. Consequently, live manifest rendering (flate/validate-pr.sh) and upstream release-note content were not independently verified.

Unknowns or Needs Verification

  • Upstream release notes for SearXNG 2026.8.5-1689cb1b5 were not fetched (GitHub releases enrichment returned no matching tags). The change is a patch-level bump within the same 2026.8.x series, so breaking-change risk is low, but the specific changelog content is unverified.
  • Live cluster validation of the rendered HelmRelease was not performed in this review; the change is confined to an image tag, so this is informational only.

@Tanguille
Tanguille merged commit f8eea46 into main Aug 4, 2026
15 of 16 checks passed
@Tanguille
Tanguille deleted the renovate/ghcr.io-searxng-searxng-2026.x branch August 4, 2026 18:26
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.

1 participant