Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
❗Important
Release Notes retrieval for this PR were skipped because no github.com credentials were available.
If you are self-hosted, please see this instruction.
Configuration
📅Schedule: (in timezone Europe/Berlin)
Branch creation
Between 12:00 AM and 08:59 AM, only on Monday (* 0-8 * * 1)
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.
👻Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
If you want to rebase/retry this PR, check this box
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| [alpine/git](https://github.com/alpine-docker/git) | digest | `03228d7` → `e8ceedc` |
| codercom/code-server | minor | `4.141.0` → `4.143.1` |
| [ghcr.io/esphome/esphome](https://esphome.io/) ([source](https://github.com/esphome/esphome)) | minor | `2026.9.1` → `2026.10.0` |
| ghostunnel/ghostunnel | patch | `v1.11.4` → `v1.11.5` |
| [nginxinc/nginx-unprivileged](https://github.com/nginx/docker-nginx-unprivileged) | digest | `378d0c3` → `b5047b9` |
---
> ⚠️ **Warning**
>
> Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/1056) for more information.
> ❗ **Important**
>
> Release Notes retrieval for this PR were skipped because no github.com credentials were available.
> If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes).
---
### Configuration
📅 **Schedule**: (in timezone Europe/Berlin)
- Branch creation
- Between 12:00 AM and 08:59 AM, only on Monday (`* 0-8 * * 1`)
- 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.
👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNTEuMiIsInVwZGF0ZWRJblZlciI6IjQ0LjE1MS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
🤖Automated review — model claude-haiku-5-5, commit e5c99655e53ff5d20f4da71bcf083051825ed522.
Automated review by the review-bot: it approves only when it found nothing red or yellow, and a human still merges. Push new commits to get a fresh review.
Summary
Renovate bump in kubernetes/apps/home-assistant/: ghostunnel v1.11.4→v1.11.5, code-server 4.141.0→4.143.1, ESPHome 2026.9.1→2026.10.0, and digest re-pins of nginx-unprivileged and alpine/git. Only image references change, with no config changes. I found no verified defect. The base is unchanged since the PR was cut (main is still c79ccfb3, mergeable: true, and the base blobs match the diff). PR #1440 touches other files, and the linked Dependency Dashboard #1056 only lists this PR.
⚪ Unverified
Upstream behaviour of the new versions. The repo-side surface is unchanged: ghostunnel flags at deployment.yaml:242-248, code-server args and /healthz probes at deployment.yaml:279-315, ESPHome port 6052 and ESPHOME_DASHBOARD_USE_PING at esphome-deployment.yaml:45-52. I could not read the ghostunnel, code-server or ESPHome release notes (the PR body says Renovate skipped them, and I have no GitHub access), so I cannot confirm that no flag was removed or changed in these releases.
Digests. The five new digests (deployment.yaml:195, 239, 278, 340; esphome-deployment.yaml:39) are well-formed 64-hex strings. I have no registry access, so I cannot confirm they resolve to the intended tag contents. The CI kustomize build does not pull images.
🟡 Suggestions
HA-impact review before merge (repo rule).kubernetes/apps/home-assistant/deployment.yaml:20 is strategy: type: Recreate, so this PR restarts the whole Home Assistant pod (and the ESPHome pod, which sits in the same directory). README.md requires a named HA-impact reviewer's statement and approval in the PR before merge for any change under kubernetes/apps/home-assistant/. It also says such changes are merged and applied only between 02:00 and 05:00 Europe/Berlin, and to treat unclear cases as disruptive. The PR has no such review (reviews and comments are empty). Automerge is disabled, so the owner merges manually. This is a merge precondition, not a code defect.
🟢 Nits
deployment.yaml:231-233 still says the sidecar was "checked locally with ghostunnel v1.11.3", while the image on line 239 is now v1.11.5. Update the comment if the check is repeated.
Tests
The change is image pins only, so there is no unit test to add. Current CI on e5c9965 passed (ci/woodpecker/pr/ci-manifests-test, which runs kustomize build on every kustomization, and ci/woodpecker/pr/ci-scripts-test). Neither starts the new images or checks their flags. Worth checking after the merge window: the HA pod is Ready with all containers running, the ghostunnel status port 16060 answers, code-server /healthz returns 200 on 8080, the ESPHome dashboard answers on 6052, and the config-sync log shows a successful reload_all.
Recommendation
Looks reasonable — no blocking issues; comments above are optional, except the README HA-impact review, which must happen before merge.
🤖 **Automated review** — model `claude-haiku-5-5`, commit `e5c99655e53ff5d20f4da71bcf083051825ed522`.
> Automated review by the `review-bot`: it approves only when it found nothing red or yellow, and a human still merges. Push new commits to get a fresh review.
---
## Summary
Renovate bump in `kubernetes/apps/home-assistant/`: ghostunnel v1.11.4→v1.11.5, code-server 4.141.0→4.143.1, ESPHome 2026.9.1→2026.10.0, and digest re-pins of nginx-unprivileged and alpine/git. Only image references change, with no config changes. I found no verified defect. The base is unchanged since the PR was cut (`main` is still `c79ccfb3`, `mergeable: true`, and the base blobs match the diff). PR #1440 touches other files, and the linked Dependency Dashboard #1056 only lists this PR.
## ⚪ Unverified
- **Upstream behaviour of the new versions.** The repo-side surface is unchanged: ghostunnel flags at `deployment.yaml:242-248`, code-server args and `/healthz` probes at `deployment.yaml:279-315`, ESPHome port 6052 and `ESPHOME_DASHBOARD_USE_PING` at `esphome-deployment.yaml:45-52`. I could not read the ghostunnel, code-server or ESPHome release notes (the PR body says Renovate skipped them, and I have no GitHub access), so I cannot confirm that no flag was removed or changed in these releases.
- **Digests.** The five new digests (`deployment.yaml:195, 239, 278, 340`; `esphome-deployment.yaml:39`) are well-formed 64-hex strings. I have no registry access, so I cannot confirm they resolve to the intended tag contents. The CI `kustomize build` does not pull images.
## 🟡 Suggestions
- **HA-impact review before merge (repo rule).** `kubernetes/apps/home-assistant/deployment.yaml:20` is `strategy: type: Recreate`, so this PR restarts the whole Home Assistant pod (and the ESPHome pod, which sits in the same directory). `README.md` requires a named HA-impact reviewer's statement and approval in the PR before merge for any change under `kubernetes/apps/home-assistant/`. It also says such changes are merged and applied only between 02:00 and 05:00 Europe/Berlin, and to treat unclear cases as disruptive. The PR has no such review (reviews and comments are empty). Automerge is disabled, so the owner merges manually. This is a merge precondition, not a code defect.
## 🟢 Nits
- `deployment.yaml:231-233` still says the sidecar was "checked locally with ghostunnel v1.11.3", while the image on line 239 is now v1.11.5. Update the comment if the check is repeated.
## Tests
The change is image pins only, so there is no unit test to add. Current CI on `e5c9965` passed (`ci/woodpecker/pr/ci-manifests-test`, which runs `kustomize build` on every kustomization, and `ci/woodpecker/pr/ci-scripts-test`). Neither starts the new images or checks their flags. Worth checking after the merge window: the HA pod is Ready with all containers running, the ghostunnel status port 16060 answers, code-server `/healthz` returns 200 on 8080, the ESPHome dashboard answers on 6052, and the config-sync log shows a successful `reload_all`.
## Recommendation
Looks reasonable — no blocking issues; comments above are optional, except the README HA-impact review, which must happen before merge.
<!-- pr-review:sha=e5c99655e53ff5d20f4da71bcf083051825ed522 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
03228d7→e8ceedc4.141.0→4.143.12026.9.1→2026.10.0v1.11.4→v1.11.5378d0c3→b5047b9Configuration
📅 Schedule: (in timezone Europe/Berlin)
* 0-8 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.
🤖 Automated review — model
claude-haiku-5-5, commite5c99655e53ff5d20f4da71bcf083051825ed522.Summary
Renovate bump in
kubernetes/apps/home-assistant/: ghostunnel v1.11.4→v1.11.5, code-server 4.141.0→4.143.1, ESPHome 2026.9.1→2026.10.0, and digest re-pins of nginx-unprivileged and alpine/git. Only image references change, with no config changes. I found no verified defect. The base is unchanged since the PR was cut (mainis stillc79ccfb3,mergeable: true, and the base blobs match the diff). PR #1440 touches other files, and the linked Dependency Dashboard #1056 only lists this PR.⚪ Unverified
deployment.yaml:242-248, code-server args and/healthzprobes atdeployment.yaml:279-315, ESPHome port 6052 andESPHOME_DASHBOARD_USE_PINGatesphome-deployment.yaml:45-52. I could not read the ghostunnel, code-server or ESPHome release notes (the PR body says Renovate skipped them, and I have no GitHub access), so I cannot confirm that no flag was removed or changed in these releases.deployment.yaml:195, 239, 278, 340;esphome-deployment.yaml:39) are well-formed 64-hex strings. I have no registry access, so I cannot confirm they resolve to the intended tag contents. The CIkustomize builddoes not pull images.🟡 Suggestions
kubernetes/apps/home-assistant/deployment.yaml:20isstrategy: type: Recreate, so this PR restarts the whole Home Assistant pod (and the ESPHome pod, which sits in the same directory).README.mdrequires a named HA-impact reviewer's statement and approval in the PR before merge for any change underkubernetes/apps/home-assistant/. It also says such changes are merged and applied only between 02:00 and 05:00 Europe/Berlin, and to treat unclear cases as disruptive. The PR has no such review (reviews and comments are empty). Automerge is disabled, so the owner merges manually. This is a merge precondition, not a code defect.🟢 Nits
deployment.yaml:231-233still says the sidecar was "checked locally with ghostunnel v1.11.3", while the image on line 239 is now v1.11.5. Update the comment if the check is repeated.Tests
The change is image pins only, so there is no unit test to add. Current CI on
e5c9965passed (ci/woodpecker/pr/ci-manifests-test, which runskustomize buildon every kustomization, andci/woodpecker/pr/ci-scripts-test). Neither starts the new images or checks their flags. Worth checking after the merge window: the HA pod is Ready with all containers running, the ghostunnel status port 16060 answers, code-server/healthzreturns 200 on 8080, the ESPHome dashboard answers on 6052, and the config-sync log shows a successfulreload_all.Recommendation
Looks reasonable — no blocking issues; comments above are optional, except the README HA-impact review, which must happen before merge.