bump GitHub Actions versions off the deprecated Node 20 runtime#219
bump GitHub Actions versions off the deprecated Node 20 runtime#219
Conversation
Action versions in .github/workflows/{ci,release}.yml and the
.github/actions/test composite action were on majors that GitHub is
deprecating (Node 20 runtime, default-removed September 2026). Bump
to current majors:
actions/checkout v3 -> v4
docker/setup-qemu-action v2.1.0 -> v3
docker/setup-buildx-action v2.2.1 -> v3
docker/login-action v2.1.0 -> v3
docker/build-push-action v3.2.0 -> v6
e1himself/goss-installation-action v1.0.4 -> v1.2.1
The composite test action now sets up Docker Buildx explicitly
before build-push-action v6 (which requires it), and passes
load: true so the built image is available to the local Docker
daemon for the subsequent dgoss run.
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe PR updates GitHub Actions workflow and test action versions. Specifically, it upgrades ChangesGitHub Actions Dependency Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 29 minutes and 48 seconds.Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/workflows/release.yml (1)
27-51: LGTM – action versions and step ordering are correct.QEMU → Buildx → Login → Build-and-push is the correct sequencing for multi-platform pushes.
push: truewith noload: trueis the right pattern for registry distribution.One minor heads-up: the current Docker docs already reference
docker/setup-qemu-action@v4,docker/setup-buildx-action@v4,docker/login-action@v4, anddocker/build-push-action@v7, though the v3/v6 combination fully resolves the Node 20 deprecation that motivates this PR.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/release.yml around lines 27 - 51, Update the GitHub Actions step versions to the newer releases referenced in the Docker docs: bump docker/setup-qemu-action@v3 → `@v4`, docker/setup-buildx-action@v3 → `@v4`, docker/login-action@v3 → `@v4`, and docker/build-push-action@v6 → `@v7` while preserving the existing step order (Set up QEMU → Set up Docker Build → Login to DockerHub → Build and push the production image) and keeping push: true (no load: true) and the platforms/tags configuration unchanged; this ensures compatibility with current Docker recommendations without changing the workflow logic.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.github/workflows/release.yml:
- Around line 27-51: Update the GitHub Actions step versions to the newer
releases referenced in the Docker docs: bump docker/setup-qemu-action@v3 → `@v4`,
docker/setup-buildx-action@v3 → `@v4`, docker/login-action@v3 → `@v4`, and
docker/build-push-action@v6 → `@v7` while preserving the existing step order (Set
up QEMU → Set up Docker Build → Login to DockerHub → Build and push the
production image) and keeping push: true (no load: true) and the platforms/tags
configuration unchanged; this ensures compatibility with current Docker
recommendations without changing the workflow logic.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a9d8eb2c-de7a-47bc-a5b1-979896ee656f
📒 Files selected for processing (3)
.github/actions/test/action.yml.github/workflows/ci.yml.github/workflows/release.yml
Per CodeRabbit review: v3 (qemu/buildx/login) and v6 (build-push) were only the previous-most-recent majors; the current latest are v4 across the docker/ actions, v7 for build-push-action, v6 for actions/checkout, and v1.3.0 for goss-installation-action. Bump everything in release.yml, ci.yml, and the composite test action.
The release workflow's run output is currently noisy with Node 20 deprecation warnings — GitHub is removing Node 20 from runners by September 2026 and forcing the default to Node 24 in June 2026. All the action versions we're pinned to ship Node 20 binaries.
Bumping every action to its current major:
actions/checkoutv3v4docker/setup-qemu-actionv2.1.0v3docker/setup-buildx-actionv2.2.1v3docker/login-actionv2.1.0v3docker/build-push-actionv3.2.0v6e1himself/goss-installation-actionv1.0.4v1.2.1Composite test action
build-push-action@v6strictly requiressetup-buildx-actionto have run first. The test composite action wasn't setting it up (the originalv3.2.0had a softer fallback). Two adjustments:docker/setup-buildx-action@v3step before the build.load: trueon the build-push-action call so the resulting image is available to the local Docker daemon — without this, buildx builds but doesn't load, and the subsequentdgoss run phanan/koel:testwould fail with "image not found."Test plan
Continuous integrationworkflow runs on PRs) exercises the test action — green confirms the buildx + load: true wiring works end-to-end.Summary by CodeRabbit
Release Notes