From bf14e8b3d090ad0851bfcbfdb7a37ea70a35b61a Mon Sep 17 00:00:00 2001 From: alexbelgium Date: Wed, 23 Sep 2026 09:23:14 +0200 Subject: [PATCH] fix(cleanuparr): drop webui, which the add-on linter rejects under ingress MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `frenck/action-addon-linter` fails the build with "'webui' should be removed, Ingress is enabled." This is pre-existing — `ingress: true` and `webui` have coexisted here for a while — but this is the first PR to touch the add-on and run the linter over it, so it blocks here. cleanuparr was the only one of the repository's 56 ingress add-ons that set `webui`; the other 55 omit it. Removing it matches both the linter and the rest of the repo. "Open Web UI" goes through ingress, and port 11011 stays published for direct access. Co-Authored-By: Claude Opus 5 --- cleanuparr/CHANGELOG.md | 3 +++ cleanuparr/config.yaml | 1 - 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/cleanuparr/CHANGELOG.md b/cleanuparr/CHANGELOG.md index 270f461a25..df091088e3 100644 --- a/cleanuparr/CHANGELOG.md +++ b/cleanuparr/CHANGELOG.md @@ -6,6 +6,9 @@ path Cleanuparr's web UI builds its asset, API and SignalR URLs from, so they resolve under the ingress path instead of the Home Assistant root. Direct access on port 11011 is unchanged (#3084) +- Remove `webui`, which the add-on linter rejects when ingress is enabled and which + the repository's other 55 ingress add-ons do not set; "Open Web UI" uses ingress + and port 11011 stays published ## 2.10.6 (2026-09-19) - Update to latest version from Cleanuparr/Cleanuparr (changelog : https://github.com/Cleanuparr/Cleanuparr/releases) diff --git a/cleanuparr/config.yaml b/cleanuparr/config.yaml index 43bcfedbfa..5e36dd70cb 100644 --- a/cleanuparr/config.yaml +++ b/cleanuparr/config.yaml @@ -92,4 +92,3 @@ schema: slug: cleanuparr url: https://github.com/alexbelgium/hassio-addons/tree/master/cleanuparr version: "2.10.6.1" -webui: "[PROTO:ssl]://[HOST]:[PORT:11011]"