[SPARK-56724][INFRA][4.2] Make docker/* GitHub Actions up-to-date#56555
Closed
sarutak wants to merge 1 commit into
Closed
[SPARK-56724][INFRA][4.2] Make docker/* GitHub Actions up-to-date#56555sarutak wants to merge 1 commit into
sarutak wants to merge 1 commit into
Conversation
This PR upgrades four docker/* GitHub Actions to the latest commit hashes approved by the Apache Software Foundation in infrastructure-actions/approved_patterns.yml: | Action | Before (tag) | After (tag) | | --- | --- | --- | | docker/build-push-action | 10e90e3645eae34f1e60eeb005ba3a3d33f178e8 (v6.19.2) | bcafcacb16a39f128d818304e6c9c0c18556b85f (v7.1.0) | | docker/login-action | c94ce9fb468520275223c153574b00df6fe4bcc9 (v3.7.0) | 4907a6ddec9925e35a0a9e82d7399ccc52663121 (v4.1.0) | | docker/setup-buildx-action | 8d2750c68a42422c14e847fe6c8ac0403b4cbd6f (v3.12.0) | 4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd (v4.0.0) | | docker/setup-qemu-action | 29109295f81e9208d7d86ff1c6c12d2833863392 (v3.6.0) | ce360397dd3f832beb865e1373c09c0e9f86d70a (v4.0.0) |
dongjoon-hyun
approved these changes
Jun 17, 2026
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
Member
There was a problem hiding this comment.
+1, LGTM. Thank you, @sarutak .
Member
Author
|
@dongjoon-hyun |
Member
|
Yes, this is for 4.2.0. |
Member
Author
|
Got it. Let's merge this soon for 4.2.0 once the CI passes. |
sarutak
pushed a commit
that referenced
this pull request
Jun 17, 2026
### What changes were proposed in this pull request? Update the commit SHAs of the following Docker-related GitHub Actions in `branch-4.2` to match the ones registered in the Apache organization's GitHub Actions allowlist: - `docker/login-action` - `docker/setup-qemu-action` - `docker/setup-buildx-action` - `docker/build-push-action` ### Why are the changes needed? The `master` branch was already updated to the new SHAs, but `branch-4.2` still had the old ones that are no longer in the allowlist. - #55687 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? CI should pass with this change. ### Was this patch authored or co-authored using generative AI tooling? Kiro CLI / Claude Closes #56555 from sarutak/update-docker-actions-branch-4.2. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Kousuke Saruta <sarutak@apache.org>
Member
Author
|
Merged to |
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
2 participants
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.
What changes were proposed in this pull request?
Update the commit SHAs of the following Docker-related GitHub Actions in
branch-4.2to match the ones registered in the Apache organization's GitHub Actions allowlist:docker/login-actiondocker/setup-qemu-actiondocker/setup-buildx-actiondocker/build-push-actionWhy are the changes needed?
The
masterbranch was already updated to the new SHAs, butbranch-4.2still had the old ones that are no longer in the allowlist.docker/*GitHub Actions up-to-date #55687Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI should pass with this change.
Was this patch authored or co-authored using generative AI tooling?
Kiro CLI / Claude