Skip to content

[SPARK-56724][INFRA][4.0] Make docker/* GitHub Actions up-to-date#56531

Open
sarutak wants to merge 1 commit into
apache:branch-4.0from
sarutak:update-docker-actions-branch-4.0
Open

[SPARK-56724][INFRA][4.0] Make docker/* GitHub Actions up-to-date#56531
sarutak wants to merge 1 commit into
apache:branch-4.0from
sarutak:update-docker-actions-branch-4.0

Conversation

@sarutak

@sarutak sarutak commented Jun 15, 2026

Copy link
Copy Markdown
Member

What changes were proposed in this pull request?

Update the commit SHAs of the following Docker-related GitHub Actions in branch-4.0 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.0 still had the old ones that are no longer in the allowlist.

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

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 dongjoon-hyun left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants