Skip to content

fix(container): update image ghcr.io/dgtlmoon/changedetection.io ( 0.53.4 ➔ 0.53.5 ) - #2208

Merged
Tanguille merged 1 commit into
mainfrom
renovate/ghcr.io-dgtlmoon-changedetection.io-0.x
Feb 20, 2026
Merged

fix(container): update image ghcr.io/dgtlmoon/changedetection.io ( 0.53.4 ➔ 0.53.5 )#2208
Tanguille merged 1 commit into
mainfrom
renovate/ghcr.io-dgtlmoon-changedetection.io-0.x

Conversation

@renovate

@renovate renovate Bot commented Feb 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/dgtlmoon/changedetection.io patch 0.53.40.53.5

Release Notes

dgtlmoon/changedetection.io (ghcr.io/dgtlmoon/changedetection.io)

v0.53.5

Compare Source

What's Changed

Full Changelog: dgtlmoon/changedetection.io@0.53.4...0.53.5


Configuration

📅 Schedule: 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 Feb 20, 2026

Copy link
Copy Markdown
Contributor

DeepSource Code Review

DeepSource reviewed changes in the commit range f27e8f5...226ff71 on this pull request. Below is the summary for the review, and you can see the individual issues we found as review comments.

For detailed review results, please see the PR on DeepSource ↗

PR Report Card

Security × 0 issues Overall PR Quality   

Reliability × 0 issues
Complexity × 0 issues
Hygiene × 0 issues

Code Review Summary

Analyzer Status Summary Details
JavaScript No new issues detected. Review ↗
Shell No new issues detected. Review ↗
How are these analyzer statuses calculated?

Administrators can configure which issue categories are reported and cause analysis to be marked as failed when detected. This helps prevent bad and insecure code from being introduced in the codebase. If you're an administrator, you can modify this in the repository's settings.

@tanguille-cluster

Copy link
Copy Markdown
--- kubernetes/apps/default/changedetection/app Kustomization: default/changedetection HelmRelease: default/changedetection

+++ kubernetes/apps/default/changedetection/app Kustomization: default/changedetection HelmRelease: default/changedetection

@@ -35,13 +35,13 @@

         containers:
           app:
             env:
               PORT: 5000
             image:
               repository: ghcr.io/dgtlmoon/changedetection.io
-              tag: 0.53.4
+              tag: 0.53.5
             resources:
               limits:
                 cpu: 100m
                 memory: 256Mi
               requests:
                 cpu: 10m

@tanguille-cluster

Copy link
Copy Markdown
--- HelmRelease: default/changedetection Deployment: default/changedetection

+++ HelmRelease: default/changedetection Deployment: default/changedetection

@@ -36,13 +36,13 @@

       hostPID: false
       dnsPolicy: ClusterFirst
       containers:
       - env:
         - name: PORT
           value: '5000'
-        image: ghcr.io/dgtlmoon/changedetection.io:0.53.4
+        image: ghcr.io/dgtlmoon/changedetection.io:0.53.5
         name: app
         resources:
           limits:
             cpu: 100m
             memory: 256Mi
           requests:

@Tanguille
Tanguille merged commit 9886f05 into main Feb 20, 2026
16 checks passed
@Tanguille
Tanguille deleted the renovate/ghcr.io-dgtlmoon-changedetection.io-0.x branch February 20, 2026 08:58
Tanguille added a commit that referenced this pull request Jul 27, 2026
The server was disabled because ToolHive's virtual-MCP health monitoring
repeatedly sends `initialize` to stdio backends, which github-mcp-server
answers with `duplicate "initialize" received`, degrading the resources and
unified gateways (upstream #5890).

The server has supported streamable-http since PR #1849, so the fix is a
transport change rather than a different vendor: `args: [http]` instead of
`[stdio]`, on v1.7.0. Read-only enforcement in http mode was broken when it
first shipped and was fixed in #2208, which is in every release from v1.0.0.

http mode does not take a server-side token - unlike the stdio path, its
ServerConfig has no Token field and it authenticates per request. So the PAT
moves from a `secrets:` env mount to an MCPExternalAuthConfig of type
bearerToken, which makes the proxy attach it as an Authorization header. This
is the first MCPExternalAuthConfig in the cluster.

Scoped to four toolsets, since the full server exposes ~79 tools and every one
of them lands in the unified gateway's semantic tool index.

Verified: the v1.7.0 image manifest exists on ghcr.io, all four objects pass
`kubectl apply --dry-run=server`, and the referenced secret key is present.
Not yet verified at runtime - the pods have not been started.
Tanguille pushed a commit that referenced this pull request Aug 21, 2026
…53.4 ➔ 0.53.5 ) (#2208)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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