Repository navigation
build(ci): bump docker actions to currently approved ASF SHAs - #46
Merged
Merged
Conversation
docker/login-action v4.4.0 (af1e73f) was pruned from the ASF allowed-actions list, so publish-docker failed at startup on main after #45. Move it to v4.6.0 and setup-buildx-action to v4.4.1, the newest approved SHAs; the v4.2.0 buildx pin expires on 2026-11-19. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hanahmily
approved these changes
Oct 18, 2026
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.
publish-dockerhit astartup_failureon main after #45 (run), becausedocker/login-action@af1e73f(v4.4.0) is no longer on the ASF approved list.This PR moves both third-party pins to the newest approved SHAs, neither of which has an expiry:
docker/login-actionaf1e73f(pruned)dbcb813docker/setup-buildx-actionbb05f3f(expires 2026-11-19)f87e599The releases in between only contain fixes and dependency bumps; nothing breaks the inputs we use.
publish-dockerruns only on push tomainand on release, so this PR's CI won't exercise it. The first run after merge will.🤖 Generated with Claude Code