From b1f5d6dcbc5fa42e33457904edcbf87ee18b91ea Mon Sep 17 00:00:00 2001 From: Claude Bot Date: Thu, 30 Jul 2026 21:49:42 +0200 Subject: [PATCH] ci: explain the ci-k8s tag split and track the stale pins (#461) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Review noted this file pins ci-k8s at a newer dated tag than e2e.yml, e2e-test.yml, alert-monitor.yml and issue-fix.yml, and asked for either a stated reason or a follow-up so it does not read as an oversight. There is no reason — the other four are stale. Per the latest-stable rule all five should sit on the newest dated tag. Not bumped here on purpose. Those four pipelines exercise different tooling in the image and three are cron- or event-triggered, so none of them run on this PR. Bumping them in this branch would ship four untested changes under cover of a green run that never touched them — the same shape as the digest decay in #458, where breakage sat unnoticed precisely because the affected jobs did not run for months. Each wants its own verification, so it is tracked as #461 rather than smuggled in here. Comment added above kustomize-build so the split is explained where a reader meets it, pointing at the issue rather than restating the whole argument. Co-Authored-By: Claude Opus 5 (1M context) --- .woodpecker/ci-manifests-test.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.woodpecker/ci-manifests-test.yml b/.woodpecker/ci-manifests-test.yml index 990df49f..8734c0e5 100644 --- a/.woodpecker/ci-manifests-test.yml +++ b/.woodpecker/ci-manifests-test.yml @@ -51,6 +51,13 @@ steps: # # Verified green across every kustomization in the tree when this was added, # so this gates new breakage rather than pre-existing debt. + # + # ci-k8s TAG SPLIT: this file pins a newer dated tag than e2e.yml, e2e-test.yml, + # alert-monitor.yml and issue-fix.yml, which still sit on an older one. That is + # staleness in those four, not a deliberate split here — everything should be on + # the newest dated tag. They are not bumped here because none of them are + # triggered by this PR, so it would ship untested changes under cover of a green + # run that never touched them. Tracked in #461. - name: kustomize-build depends_on: [] # see note above `steps:` image: gitea.renner.uno/gitea_admin/ci-k8s:2026-07-30