chore(ci): bump alpine to 3.24.1 in deploy-infrastructure #551

Merged
k.renner merged 1 commits from bump-stale-ci-images into master 2026-08-23 20:59:55 +00:00
Member
alpine  3.21 -> 3.24.1   (.woodpecker/deploy-infrastructure.yml)

Tag verified present before bumping. From the #426 audit.

Refs #426

``` alpine 3.21 -> 3.24.1 (.woodpecker/deploy-infrastructure.yml) ``` Tag verified present before bumping. From the #426 audit. Refs #426
review-bot left a comment
Member

🤖 Automated review — model claude-haiku-4-5-20251001 (complexity: trivial), commit a5570a665002d83c48dc688a5d0ec88471ef01a8.

Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.


Summary

This PR bumps two base images used in CI pipelines: kaniko-project/executor from v1.23.2-debug to v1.24.0-debug (9 occurrences) and alpine from 3.21 to 3.24.1 (1 occurrence). The tags have been verified to exist, the PR body documents the motivation clearly, and all occurrences across the relevant files have been updated consistently.

🔴 Blocking

None.

🟡 Suggestions

None. The PR is well-documented with appropriate context about the kaniko project being archived and the long-term implications tracked separately in #552.

🟢 Nits

None.

Tests

This is a CI infrastructure change (image tag bumps), not application code. The tags were verified by the author before bumping via docker manifest inspect. The alpine change targets a simple validation step that checks environment variables (.woodpecker/deploy-infrastructure.yml:15-26), which is fully compatible with alpine 3.24.1. No test coverage gap.

Recommendation

Looks reasonable — no blocking issues. All changes are consistent and complete.

🤖 **Automated review** — model `claude-haiku-4-5-20251001` (complexity: trivial), commit `a5570a665002d83c48dc688a5d0ec88471ef01a8`. > Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review. --- ## Summary This PR bumps two base images used in CI pipelines: kaniko-project/executor from v1.23.2-debug to v1.24.0-debug (9 occurrences) and alpine from 3.21 to 3.24.1 (1 occurrence). The tags have been verified to exist, the PR body documents the motivation clearly, and all occurrences across the relevant files have been updated consistently. ## 🔴 Blocking None. ## 🟡 Suggestions None. The PR is well-documented with appropriate context about the kaniko project being archived and the long-term implications tracked separately in #552. ## 🟢 Nits None. ## Tests This is a CI infrastructure change (image tag bumps), not application code. The tags were verified by the author before bumping via `docker manifest inspect`. The alpine change targets a simple validation step that checks environment variables (`.woodpecker/deploy-infrastructure.yml:15-26`), which is fully compatible with alpine 3.24.1. No test coverage gap. ## Recommendation Looks reasonable — no blocking issues. All changes are consistent and complete. <!-- pr-review:sha=a5570a665002d83c48dc688a5d0ec88471ef01a8 -->
claude-bot force-pushed bump-stale-ci-images from a5570a6650 to 5b6a55c8ba 2026-08-21 20:55:10 +00:00 Compare
claude-bot changed title from chore(ci): bump kaniko to v1.24.0-debug and alpine to 3.24.1 to chore(ci): bump alpine to 3.24.1 in deploy-infrastructure 2026-08-21 20:55:18 +00:00
review-bot left a comment
Member

🤖 Automated review — model claude-haiku-4-5-20251001 (complexity: trivial), commit 5b6a55c8ba315493977ed77dbf48bf814924405a.

Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.


Summary

This PR bumps the Alpine Linux image from 3.21 to 3.24.1 in the validate-secrets step of .woodpecker/deploy-infrastructure.yml. The change is minimal, the tag has been verified, and the scope is intentionally limited per the referenced audit.

🔴 Blocking

None — no blocking issues found.

🟡 Suggestions

Scope clarification for follow-up work: The PR correctly limits itself to .woodpecker/deploy-infrastructure.yml, but the grep search reveals 20+ other alpine:3.21 references in the repository:

  • Containerfiles in ci/images/ (ansible, k8s, tofu, alpine-jq, alpine-openssl, cni-plugins)
  • Kubernetes manifests (mosquitto-bootstrap.yaml, ftp-scanner.yaml, cni-dhcp-daemon.yaml)
  • Test and migration scripts (e2e-test.sh, velero/restore-test.sh)

The PR body notes this is from audit #426 and references #552 for the kaniko migration. This suggests the broader Alpine bump is being tracked separately, which is reasonable. However, it's worth confirming in the issue tracker that those other occurrences are in scope for a follow-up PR, not accidentally left behind.

🟢 Nits

None.

Tests

This is a CI configuration change. The validate-secrets step runs a simple shell script that checks for required secrets — the Alpine version bump is backward-compatible and won't affect the script's behavior. The change will be validated when the pipeline next runs.

Recommendation

Looks reasonable — no blocking issues; the scope suggestion above is optional.

🤖 **Automated review** — model `claude-haiku-4-5-20251001` (complexity: trivial), commit `5b6a55c8ba315493977ed77dbf48bf814924405a`. > Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review. --- ## Summary This PR bumps the Alpine Linux image from 3.21 to 3.24.1 in the `validate-secrets` step of `.woodpecker/deploy-infrastructure.yml`. The change is minimal, the tag has been verified, and the scope is intentionally limited per the referenced audit. ## 🔴 Blocking None — no blocking issues found. ## 🟡 Suggestions **Scope clarification for follow-up work**: The PR correctly limits itself to `.woodpecker/deploy-infrastructure.yml`, but the grep search reveals 20+ other alpine:3.21 references in the repository: - Containerfiles in `ci/images/` (ansible, k8s, tofu, alpine-jq, alpine-openssl, cni-plugins) - Kubernetes manifests (mosquitto-bootstrap.yaml, ftp-scanner.yaml, cni-dhcp-daemon.yaml) - Test and migration scripts (e2e-test.sh, velero/restore-test.sh) The PR body notes this is from audit #426 and references #552 for the kaniko migration. This suggests the broader Alpine bump is being tracked separately, which is reasonable. However, it's worth confirming in the issue tracker that those other occurrences are in scope for a follow-up PR, not accidentally left behind. ## 🟢 Nits None. ## Tests This is a CI configuration change. The `validate-secrets` step runs a simple shell script that checks for required secrets — the Alpine version bump is backward-compatible and won't affect the script's behavior. The change will be validated when the pipeline next runs. ## Recommendation Looks reasonable — no blocking issues; the scope suggestion above is optional. <!-- pr-review:sha=5b6a55c8ba315493977ed77dbf48bf814924405a -->
k.renner merged commit 89582c9c9f into master 2026-08-23 20:59:55 +00:00
Sign in to join this conversation.