Skip to content

RED-198334 Bump GH Actions off Node 20 (release/8.0)#535

Closed
gonen-red wants to merge 1 commit into
redis:release/8.0from
gonen-red:RED-198334_release-8.0
Closed

RED-198334 Bump GH Actions off Node 20 (release/8.0)#535
gonen-red wants to merge 1 commit into
redis:release/8.0from
gonen-red:RED-198334_release-8.0

Conversation

@gonen-red

@gonen-red gonen-red commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

Summary

RED-198334. Cherry-pick of the canonical Node 20 -> Node 24 bump from unstable (#526), plus 5 extra bumps unique to release/8.0. Targets release/8.0.

Canonical CP:

  • Bump first-party actions: actions/checkout@v4 -> @v6 (16 sites), actions/upload-artifact@v4 -> @v7 (5 sites), actions/download-artifact@v4 -> @v7
  • Bump docker/* actions: setup-buildx v3->v4, login v3->v4 (4 sites), build-push v6->v7 (2 sites)
  • Bump dorny/test-reporter v2->v3, peter-evans/create-pull-request v7->v8, iarekylew00t/verified-bot-commit v1->v2

release/8.0 extras (build_release_automation.yml exists only on this branch):

  • actions/checkout@v4 -> @v6
  • docker/setup-buildx-action@v3 -> @v4
  • docker/metadata-action@v5 -> @v6
  • docker/build-push-action@v5 -> @v7
  • docker/login-action@v3 -> @v4

Test plan

  • pull-request.yml runs cleanly on this PR
  • On next release tag, release_build_and_test.yml produces same image digests
  • build_release_automation.yml builds the release automation Docker image cleanly with bumped actions

Note

Medium Risk
Touches every major pipeline (PR, nightly-style build, release build/publish, and GHCR tagging) via action major-version jumps; failures would block merges and releases but do not change Redis image build recipes.

Overview
RED-198334 — Cherry-pick to release/8.0 that moves CI off GitHub Actions’ Node 20 runtime by bumping third-party action pins across composite actions and workflows. No application or Docker image logic changes.

First-party actions: actions/checkout v4 → v6, actions/upload-artifact and actions/download-artifact v4 → v7 everywhere they appear (PR validation, build/test, release handle/info artifacts, image metadata).

Docker-related actions: docker/setup-buildx-action v3 → v4, docker/login-action v3 → v4, docker/build-push-action v6 → v7 (and v5 → v7 in build_release_automation.yml). docker/metadata-action v5 → v6 only in that release-automation workflow.

Other bumps: dorny/test-reporter v2 → v3, peter-evans/create-pull-request v7 → v8, iarekylew00t/verified-bot-commit v1 → v2 for release version commits.

Reviewed by Cursor Bugbot for commit a5a048e. Bugbot is set up for automated code reviews on this repo. Configure here.

Cherry-pick of the canonical unstable fix, plus 5 additional bumps in
build_release_automation.yml (a file that exists only on release/8.0).

Canonical CP:
- Bump first-party actions: actions/checkout@v4 -> @v6 (16 sites), actions/upload-artifact@v4 -> @v7 (5 sites), actions/download-artifact@v4 -> @v7
- Bump docker/* actions: setup-buildx v3->v4 (3 sites), login v3->v4 (4 sites), build-push v6->v7 (2 sites)
- Bump dorny/test-reporter v2->v3, peter-evans/create-pull-request v7->v8, iarekylew00t/verified-bot-commit v1->v2

release/8.0 extras (build_release_automation.yml):
- actions/checkout@v4 -> @v6
- docker/setup-buildx-action@v3 -> @v4
- docker/metadata-action@v5 -> @v6
- docker/build-push-action@v5 -> @v7
- docker/login-action@v3 -> @v4

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Peter-Sh

Peter-Sh commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Thanks, I did it by merging your unstable PR into release branches.

@Peter-Sh Peter-Sh closed this Jun 9, 2026
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