Skip to content

chore(deps): bump the three pinned docker/* actions in one change - #308

Merged
dvcdsys merged 1 commit into
developfrom
chore/bump-docker-actions
Nov 3, 2026
Merged

dvcdsys merged 1 commit into
developfrom
chore/bump-docker-actions

Conversation

@dvcdsys

@dvcdsys dvcdsys commented Nov 3, 2026

Copy link
Copy Markdown
Owner

Collapses #293, #305 and #294 into one change.

action from to
docker/setup-buildx-action v4.2.0 v4.4.1
docker/login-action v4.5.1 v4.7.0
docker/build-push-action v7.3.0 v7.4.0

Why one PR instead of three

All three uses: lines sit within three lines of each other — release-server.yml 69/72/78 and 129/137/143, prerelease-server.yml 31/39/45. With git's default three lines of context their hunks overlap, so merging any one of the three leaves the other two conflicted and needing @dependabot rebase before they can go in. One change removes two rebase rounds and two merges.

Verification

Each SHA was taken from the corresponding Dependabot diff and then cross-checked against the upstream release tag through the GitHub API, so each pin is provably the commit its tag points at:

docker/setup-buildx-action v4.4.1 = f87e5991a6d7451dcb8d9637bfbc97413f497069
docker/login-action        v4.7.0 = 81c6f93d4bc991e510b342a00b419b3bb4efc5c6
docker/build-push-action   v7.4.0 = c3c9e263c25d99ce0380d002d59b67737d91b0dc

Scope: 10 changed lines, every one of them a uses: line, across the three workflows that reference these actions — release-server.yml (both the CPU multi-arch job and the CUDA job), prerelease-server.yml, and llama-pin-check.yml (setup-buildx only). No old pin remains anywhere under .github/.

Once this lands, #293, #305 and #294 can be closed as superseded — Dependabot will not reopen them, since each dependency is already at the version it asked for.

🤖 Generated with Claude Code

Collapses Dependabot PRs #293, #305 and #294 into a single change.

    docker/setup-buildx-action  v4.2.0 -> v4.4.1  (10 -> 3 occurrences updated)
    docker/login-action         v4.5.1 -> v4.7.0
    docker/build-push-action    v7.3.0 -> v7.4.0

Why one PR instead of three: all three `uses:` lines sit within three lines
of each other in `release-server.yml` (69/72/78 and 129/137/143) and in
`prerelease-server.yml` (31/39/45). With git's default three lines of
context their diff hunks overlap, so merging any one of the three Dependabot
PRs leaves the other two conflicted and needing `@dependabot rebase` before
they can go in. Doing all three at once removes two rebase rounds and two
merges.

Each SHA was taken from the corresponding Dependabot diff and then
cross-checked against the upstream release tag via the GitHub API, so the
pin is provably the commit the tag points at:

    docker/setup-buildx-action v4.4.1 = f87e5991a6d7451dcb8d9637bfbc97413f497069
    docker/login-action        v4.7.0 = 81c6f93d4bc991e510b342a00b419b3bb4efc5c6
    docker/build-push-action   v7.4.0 = c3c9e263c25d99ce0380d002d59b67737d91b0dc

Scope check: the only lines this touches are `uses:` lines, in the three
workflows that reference these actions -- `release-server.yml` (both the
CPU multi-arch job and the CUDA job), `prerelease-server.yml`, and
`llama-pin-check.yml` (setup-buildx only). No old pin remains anywhere
under `.github/`.

After this lands, close #293, #305 and #294 as superseded; Dependabot will
not reopen them, since the dependency is already at the requested version.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@dvcdsys
dvcdsys merged commit b548e03 into develop Nov 3, 2026
7 checks passed
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.

1 participant