feat(container): update image ghcr.io/coder/code-server (4.138.0 ➔ 4.139.1)

renovate-bot commented

2026-09-26 03:01:45 +02:00

Collaborator

This PR contains the following updates:

Package	Update	Change
ghcr.io/coder/code-server	minor	`4.138.0` → `4.139.1`

⚠️ Warning

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

Configuration

📅 Schedule: (in timezone Europe/Rome)

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 has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | ghcr.io/coder/code-server | minor | `4.138.0` → `4.139.1` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/6) for more information. --- ### Configuration 📅 **Schedule**: (in timezone Europe/Rome) - 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 has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).

renovate-bot added the

renovate/container

type/minor

labels

2026-09-26 03:01:45 +02:00

renovate-bot added 1 commit

2026-09-26 03:01:45 +02:00

feat(container): update image ghcr.io/coder/code-server (4.138.0 ➔ 4.139.1)

Labeler / Labeler (pull_request) Successful in 4s

Details

Lint / actionlint (pull_request) Successful in 6s

Details

Lint / yamllint (pull_request) Successful in 13s

Details

AI PR Review / AI PR Review (pull_request) Successful in 44s

Details

Konflate 2 resources changed

Details

7c0ec9efb6

forgejo-actions added the

area/kubernetes

label

2026-09-26 03:01:49 +02:00

lab-assistant-bot commented

2026-09-26 03:01:49 +02:00

Collaborator

Routine: only container-image and chart-version changes; 2 resources across 2 apps

image	from	to	upstream
`ghcr.io/coder/code-server`	`4.138.0@sha256:81706b…`	`4.139.1@sha256:0c067c…`	❔

_{konflate 0.6.4 · rendered 7c0ec9e · full diff →}

**Routine**: only container-image and chart-version changes; 2 resources across 2 apps | image | from | to | upstream | |---|---|---|---| | `ghcr.io/coder/code-server` | `4.138.0@sha256:81706b…` | `4.139.1@sha256:0c067c…` | ❔ | <sub>konflate 0.6.4 · rendered `7c0ec9e` · [full diff →](https://konflate.aresu.eu/#/pr/2221)</sub>

lab-assistant-bot commented

2026-09-26 03:02:28 +02:00

Collaborator

✅ Automated recommendation: APPROVE

Analysis engine: minimax/MiniMax-M2-7-anthropic@http://litellm.ai.svc.cluster.local:4000/v1 (anthropic)

Recommendation: Approve

Routine Renovate container image bump for the code-server sidecar in the zigbee2mqtt HelmRelease. No functional changes beyond the version/tag update.

Changes

File	Change
`kubernetes/apps/home-automation/zigbee2mqtt/app/helmrelease.yaml`	`ghcr.io/coder/code-server` `4.138.0` → `4.139.1` (with new `@sha256:` digest)

Required Checks — Addressed

Validate manifest against target cluster version — ✅ Verified

The manifest is a HelmRelease using apiVersion: helm.toolkit.fluxcd.io/v2, a stable Flux API. No Kubernetes API version changes are involved — this is purely a container image reference bump. The HelmRelease schema validates correctly (yamlls schema present in the file).

Check for resource quota / limit changes — ✅ Verified (not applicable)

The code-server container's resources block (requests.cpu: 10m, limits.memory: 512Mi) is unchanged. Only the image.tag field was modified.

Standards Compliance

Per .agents/instructions/pr-review.instructions.md and AGENTS.md:

Container images are correctly pinned with both version tag and @sha256: digest (new image includes full digest sha256:0c067c3cf09ed…). ✅
metadata.namespace is absent from the HelmRelease — intentional per repo convention; namespace is injected at build time via kustomize. ✅
No resource limit changes that would affect cluster quota. ✅

Evidence Provider Findings

Konflate rendered diff confirms:

Deployment home-automation/zigbee2mqtt — only image tag changed (ghcr.io/coder/code-server:4.138.0 → 4.139.1)
All other fields (resources, persistence, route, security context) — unchanged
Render exit code 0, no warnings or errors

Caveat

The upstream release source for coder/code-server 4.139.1 could not be confirmed via the GitHub API lookup in the corpus (GH API enrichment returned no release data). This is a minor upstream-verification gap for a patch/minor image bump; it does not block approval given the routine nature of the change and the pinned digest providing image integrity.

✅ **Automated recommendation: APPROVE** _Analysis engine: minimax/MiniMax-M2-7-anthropic@http://litellm.ai.svc.cluster.local:4000/v1 (anthropic)_ **Recommendation: Approve** Routine Renovate container image bump for the code-server sidecar in the zigbee2mqtt HelmRelease. No functional changes beyond the version/tag update. --- ## Changes | File | Change | |---|---| | `kubernetes/apps/home-automation/zigbee2mqtt/app/helmrelease.yaml` | `ghcr.io/coder/code-server` `4.138.0` → `4.139.1` (with new `@sha256:` digest) | --- ## Required Checks — Addressed **Validate manifest against target cluster version** — ✅ Verified - The manifest is a `HelmRelease` using `apiVersion: helm.toolkit.fluxcd.io/v2`, a stable Flux API. No Kubernetes API version changes are involved — this is purely a container image reference bump. The HelmRelease schema validates correctly (yamlls schema present in the file). **Check for resource quota / limit changes** — ✅ Verified (not applicable) - The code-server container's `resources` block (`requests.cpu: 10m`, `limits.memory: 512Mi`) is unchanged. Only the `image.tag` field was modified. --- ## Standards Compliance Per `.agents/instructions/pr-review.instructions.md` and `AGENTS.md`: - Container images are correctly pinned with both version tag and `@sha256:` digest (new image includes full digest `sha256:0c067c3cf09ed…`). ✅ - `metadata.namespace` is absent from the `HelmRelease` — intentional per repo convention; namespace is injected at build time via kustomize. ✅ - No resource limit changes that would affect cluster quota. ✅ ## Evidence Provider Findings Konflate rendered diff confirms: - Deployment `home-automation/zigbee2mqtt` — only image tag changed (`ghcr.io/coder/code-server:4.138.0` → `4.139.1`) - All other fields (resources, persistence, route, security context) — unchanged - Render exit code 0, no warnings or errors ## Caveat The upstream release source for `coder/code-server` 4.139.1 could not be confirmed via the GitHub API lookup in the corpus (GH API enrichment returned no release data). This is a minor upstream-verification gap for a patch/minor image bump; it does not block approval given the routine nature of the change and the pinned digest providing image integrity.

GiorgioAresu merged commit aa98ecf871 into main

2026-09-26 07:44:55 +02:00

GiorgioAresu referenced this pull request from a commit

2026-09-26 07:44:56 +02:00

feat(container): update image ghcr.io/coder/code-server (4.138.0 ➔ 4.139.1) (#2221)

Rows
Columns

feat(container): update image ghcr.io/coder/code-server (4.138.0 ➔ 4.139.1) #2221

Configuration

Changes

Required Checks — Addressed

Standards Compliance

Evidence Provider Findings

Caveat