Summary
Bump the GitHub Actions used across all workflows on 6.2.x to their current major versions, mirroring the update just landed on the uv branch in #204 and tracked for 6.1.x in its sibling issue.
Motivation
All five workflows on 6.2.x still pin older action majors:
| Action |
Current on 6.2.x |
Target |
actions/checkout |
v4 |
v6 |
docker/metadata-action |
v5 |
v6 |
docker/setup-qemu-action |
v3 |
v4 |
docker/setup-buildx-action |
v3 |
v4 |
docker/login-action |
v3 |
v4 |
docker/build-push-action |
v4 (nightly, test) / v6 (image-release) |
v7 |
peter-evans/dockerhub-description |
v4 |
v5 |
Keeping these current reduces the window for deprecation warnings (GitHub has been retiring older Node runtimes fast) and keeps 6.2.x in sync with the UV and 6.1.x tracks so we're not tracking three sets of pinned versions.
Files to update
.github/workflows/description.yml
.github/workflows/image-release.yml
.github/workflows/nightly.yml
.github/workflows/release.yml
.github/workflows/test.yml
Acceptance criteria
Summary
Bump the GitHub Actions used across all workflows on
6.2.xto their current major versions, mirroring the update just landed on theuvbranch in #204 and tracked for6.1.xin its sibling issue.Motivation
All five workflows on
6.2.xstill pin older action majors:6.2.xactions/checkoutdocker/metadata-actiondocker/setup-qemu-actiondocker/setup-buildx-actiondocker/login-actiondocker/build-push-actionpeter-evans/dockerhub-descriptionKeeping these current reduces the window for deprecation warnings (GitHub has been retiring older Node runtimes fast) and keeps
6.2.xin sync with the UV and6.1.xtracks so we're not tracking three sets of pinned versions.Files to update
.github/workflows/description.yml.github/workflows/image-release.yml.github/workflows/nightly.yml.github/workflows/release.yml.github/workflows/test.ymlAcceptance criteria
6.2.xuse the target major versions listed above.test.ymlruns green on a PR against6.2.x.workflow_dispatchofrelease.ymlon the branch successfully builds and pushes images (or at least passes the build step in dry-run).news/<issue>.internal) documents the change.