konairius/homelab
10
0
Fork 0
Code Issues 8 Pull Requests 3 Packages Projects Releases 1 Wiki Activity

Bump the four stale ci-k8s:2026-05-01 pipeline pins #461

New Issue
Closed
opened 2026-07-30 19:49:16 +00:00 by claude-bot · 0 comments
claude-bot commented 2026-07-30 19:49:16 +00:00
Member
Copy Link
Copy Source

Raised by review on #460.

.woodpecker/ci-manifests-test.yml (new in #460) pins ci-k8s:2026-07-30, while four existing pipelines still pin ci-k8s:2026-05-01:

  • .woodpecker/e2e-test.yml:7
  • .woodpecker/e2e.yml:33
  • .woodpecker/alert-monitor.yml:45
  • .woodpecker/issue-fix.yml:52

There is no deliberate reason for the split — the older pins are simply stale. Per the standing rule that any software runs the latest stable version, all five should be on the newest dated tag.

Deliberately NOT done inside #460: those four pipelines exercise different tooling inside the image, and three are cron- or event-triggered, so none are run by that PR own CI. Bumping them there would ship four untested changes under cover of a green run that never touched them — the same shape as the digest-pin decay in #458, where breakage sat unnoticed because the affected jobs did not run for months.

Each bump wants its own verification that the pipeline still passes on the newer image. build-k8s only mints a new dated tag when ci/images/k8s/** or build-ci-images.yml changes on a push, so the tag set is stable between such edits and this is not urgent — but it should not be left to rot, since a stale pin eventually points at a garbage-collected tag.

Raised by review on #460. `.woodpecker/ci-manifests-test.yml` (new in #460) pins `ci-k8s:2026-07-30`, while four existing pipelines still pin `ci-k8s:2026-05-01`: - `.woodpecker/e2e-test.yml:7` - `.woodpecker/e2e.yml:33` - `.woodpecker/alert-monitor.yml:45` - `.woodpecker/issue-fix.yml:52` There is no deliberate reason for the split — the older pins are simply stale. Per the standing rule that any software runs the latest stable version, all five should be on the newest dated tag. Deliberately NOT done inside #460: those four pipelines exercise different tooling inside the image, and three are cron- or event-triggered, so none are run by that PR own CI. Bumping them there would ship four untested changes under cover of a green run that never touched them — the same shape as the digest-pin decay in #458, where breakage sat unnoticed because the affected jobs did not run for months. Each bump wants its own verification that the pipeline still passes on the newer image. `build-k8s` only mints a new dated tag when `ci/images/k8s/**` or `build-ci-images.yml` changes on a push, so the tag set is stable between such edits and this is not urgent — but it should not be left to rot, since a stale pin eventually points at a garbage-collected tag.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
apollo
Hermes expert: Immich, Audiobookshelf, Libation, Navidrome, Music Assistant
 atlas
Hermes expert: Talos, Flux, network, Authentik, Matrix, monitoring
 clio
Hermes expert: Paperless, wiki, ical-proxy, TRMNL, websites
 daedalus
Hermes expert: Gitea, Woodpecker, Renovate, review-bot, Hermes
 hestia
Hermes expert: Home Assistant, IoT, MQTT, ESPHome, voice
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
alert-monitor-bot claude-bot (Claude Bot) flux hermes-bot issue-fix-bot k.renner renovate-bot review-bot (Review Bot) security-bot update-audit-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: konairius/homelab#461