fix(ci): pin docker/* actions to current ASF allowlisted SHAs - #9095
Open
mfrancisc wants to merge 1 commit into
Open
fix(ci): pin docker/* actions to current ASF allowlisted SHAs#9095mfrancisc wants to merge 1 commit into
mfrancisc wants to merge 1 commit into
Conversation
Build-Images-Push-Docker fails at startup because the docker/* SHAs from apache#8852 were dropped from the ASF allowlist, so v1.0.3-beta16 images were never published (apache#9094). Co-Authored-By: Cursor Grok 4.6 <noreply@example.com> Co-authored-by: Cursor <cursoragent@cursor.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Build-Images-Push-Dockerfails at workflow startup because thedocker/*action SHAs pinned were removed from the ASF GitHub Actions allowlist. GitHub never starts the jobs, so release tags such asv1.0.3-beta16publish compose files but no Docker Hub images.Re-pin the four actions in
.github/workflows/build.ymlto the newest SHAs currently listed in apache/infrastructure-actionsapproved_patterns.yml:docker/setup-qemu-actionv4.0.0 → v4.2.0 (96fe6ef7)docker/setup-buildx-actionv4.0.0 → v4.3.0 (37fe6310)docker/login-actionv4.1.0 → v4.6.0 (dbcb8138)docker/build-push-actionv7.1.0 → v7.3.0 (53b7df96)setup-qemu-actionv4.3.0 exists but is not on the allowlist, so qemu stays on v4.2.0.Does this close any open issues?
Closes #9094
Screenshots
N/A
Other Information
Failed run: https://github.com/apache/devlake/actions/runs/33074025058
Same class of failure as #8851 / #8852. After this lands, re-run
Build-Images-Push-Dockeron tagv1.0.3-beta16(or retag) so Hub actually gets the images.Note: tag
v1.0.3-alpha1got past startup and then failed inbuild-devlake(make allexit 2). That is a separate image-build issue and is not addressed here.