Skip to content

ci: upgrade remaining Node.js 20 actions to Node.js 24 in gateway-discord#397

Open
hanzlamateen wants to merge 1 commit intodevfrom
fix/upgrade-remaining-node20-actions
Open

ci: upgrade remaining Node.js 20 actions to Node.js 24 in gateway-discord#397
hanzlamateen wants to merge 1 commit intodevfrom
fix/upgrade-remaining-node20-actions

Conversation

@hanzlamateen
Copy link
Collaborator

Follow-up to #395. Upgrades all remaining actions flagged for Node.js 20 deprecation in the gateway-discord workflow.

Changes

Action Old New
dorny/paths-filter v3 v4
hashicorp/setup-terraform v3 v4
docker/setup-buildx-action v3 v4
docker/login-action v3 v4
docker/metadata-action v5 v6
docker/build-push-action v6 v7

azure/setup-kubectl@v4 and azure/setup-helm@v4 kept as-is — no Node.js 24 versions available yet.

Context

After merging #395 and running the full gateway-discord pipeline via workflow_dispatch, all jobs passed (Detect Changes, Test, Build Image, Terraform, Deploy) but produced Node.js 20 deprecation warnings for the above actions. This PR clears those warnings before the June 2, 2026 forced migration.

Made with Cursor

…cord

Upgrades all actions still flagged for Node.js 20 deprecation:
- dorny/paths-filter v3 → v4
- hashicorp/setup-terraform v3 → v4
- docker/setup-buildx-action v3 → v4
- docker/login-action v3 → v4
- docker/metadata-action v5 → v6
- docker/build-push-action v6 → v7

azure/setup-kubectl@v4 and azure/setup-helm@v4 kept as-is (no
Node.js 24 versions available yet).

Made-with: Cursor
@vercel
Copy link

vercel bot commented Mar 17, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
eliza-cloud-v2 Ready Ready Preview, Comment Mar 17, 2026 1:27am

@coderabbitai
Copy link

coderabbitai bot commented Mar 17, 2026

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cb7dcbf3-6d51-46a7-9361-27cb2b643126

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/upgrade-remaining-node20-actions
📝 Coding Plan
  • Generate coding plan for human review comments

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

You can enable review details to help with troubleshooting, context usage and more.

Enable the reviews.review_details setting to include review details such as the model used, the time taken for each step and more in the review comments.

@claude
Copy link

claude bot commented Mar 17, 2026

Code Review

Summary: Straightforward CI maintenance PR upgrading 6 GitHub Actions to Node.js 24-compatible major versions. Changes are correct and well-scoped.

Review

Correctness
All version bumps are consistent with official releases:

  • dorny/paths-filter v3 → v4
  • hashicorp/setup-terraform v3 → v4
  • docker/setup-buildx-action v3 → v4
  • docker/login-action v3 → v4
  • docker/metadata-action v5 → v6
  • docker/build-push-action v6 → v7

The coordinated Docker action upgrades (buildx v4, build-push v7) are compatible with each other as expected.

Scope
Diff is minimal and focused — only the action version strings change, no logic affected. The gateway-webhook.yml workflow doesn't use any of these actions so nothing else needs updating.

Omissions noted
The decision to keep azure/setup-kubectl@v4 and azure/setup-helm@v4 as-is is correct since no Node.js 24 versions are available for those actions yet.

Minor observation: Actions are pinned to major version tags (e.g., @v4) rather than commit SHAs. This is an existing pattern in the repo rather than something introduced here, so it's not a blocker — just worth tracking if supply-chain hardening becomes a priority.

Verdict: No issues found. Safe to merge.

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