ci: bump docker job actions - #52
Merged
rnovatorov merged 1 commit intoSep 23, 2026
Merged
rnovatorov merged 1 commit into
rnovatorov merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
the docker jobs still pin node16-era majors (checkout v2, buildx/login v1, metadata v3, build-push v2) which run on forced compatibility shims and emit deprecation warnings. bump to current stable majors; build-push v7 needs runner v2.327.1+ which ubuntu-latest satisfies. checkout is aligned to v4 (not v7) to match the rest of ci.yml and keep one major per action repo-wide.
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
1 participant
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
Bumps the GitHub Actions used by the two Docker publish jobs (push_to_docker_hub, push_to_enapter_docker_hub) from node16-era majors to current stable versions. Only action versions change — no job logic, inputs, secrets, names, or conditions are touched.
Rationale
CI note
These Docker jobs only trigger on v* tags, so this PR's own CI run will show them as skipping — the run_checks matrix is the only visible check here. The first real exercise of the bumped actions happens at the next release tag.