Skip to content

Upgrade GitHub Actions to latest versions#209

Open
salmanmkc wants to merge 1 commit intoruvnet:mainfrom
salmanmkc:upgrade-github-actions-node24-general
Open

Upgrade GitHub Actions to latest versions#209
salmanmkc wants to merge 1 commit intoruvnet:mainfrom
salmanmkc:upgrade-github-actions-node24-general

Conversation

@salmanmkc
Copy link

Summary

Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.

Changes

Action Old Version(s) New Version Release Files
actions-rust-lang/setup-rust-toolchain v1 v1.15.2 Release postgres-extension-ci.yml, ruvector-postgres-ci.yml
benchmark-action/github-action-benchmark v1 v1.20.7 Release benchmarks.yml, postgres-extension-ci.yml, ruvector-postgres-ci.yml
codecov/codecov-action v4 v5 Release agentic-synth-ci.yml
docker/build-push-action v5 v6 Release docker-publish.yml, postgres-extension-ci.yml, ruvector-postgres-ci.yml
google-github-actions/auth v2 v3 Release edge-net-models.yml
google-github-actions/setup-gcloud v2 v3 Release edge-net-models.yml
peter-evans/create-or-update-comment v4 v5 Release edge-net-models.yml
peter-evans/dockerhub-description v4 v5 Release docker-publish.yml
softprops/action-gh-release v1 v2 Release publish-all.yml, release.yml

Why upgrade?

Keeping GitHub Actions up to date ensures:

  • Security: Latest security patches and fixes
  • Features: Access to new functionality and improvements
  • Compatibility: Better support for current GitHub features
  • Performance: Optimizations and efficiency improvements

⚠️ Breaking Changes

  • codecov/codecov-action (v4 → v5): Major version upgrade — review the release notes for breaking changes
    • ⚠️ Input file was removed — if your workflow uses it, the step may fail
    • ⚠️ Input plugin was removed — if your workflow uses it, the step may fail
  • softprops/action-gh-release (v1 → v2): Major version upgrade — review the release notes for breaking changes
  • docker/build-push-action (v5 → v6): Major version upgrade — review the release notes for breaking changes
  • google-github-actions/auth (v2 → v3): Major version upgrade — review the release notes for breaking changes
    • ⚠️ Input retries was removed — if your workflow uses it, the step may fail
    • ⚠️ Input backoff was removed — if your workflow uses it, the step may fail
    • ⚠️ Input backoff_limit was removed — if your workflow uses it, the step may fail
  • google-github-actions/setup-gcloud (v2 → v3): Major version upgrade — review the release notes for breaking changes
    • ⚠️ Input skip_tool_cache was removed — if your workflow uses it, the step may fail
  • peter-evans/create-or-update-comment (v4 → v5): Major version upgrade — review the release notes for breaking changes
  • peter-evans/dockerhub-description (v4 → v5): Major version upgrade — review the release notes for breaking changes

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
Copy link
Owner

@ruvnet ruvnet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @salmanmkc. A few concerns on the version bumps:

Action versions that need verification:

  • actions/checkout@v6 — as of Feb 2026, the latest stable is v4. Does v6 exist?
  • actions/upload-artifact@v6 — latest stable is v4. Same concern.
  • actions/download-artifact@v7 — latest stable is v4.
  • actions/setup-node@v6 — latest stable is v4.
  • actions/setup-python@v6 — latest stable is v5.

If these tags don't exist on the official repos, the workflows will fail. More critically, if someone creates a fork with those tags, it becomes a supply chain attack vector — the workflow would pull code from an attacker-controlled repo.

Recommendation: Please verify each action version exists on the official GitHub Actions repos before this can be merged. If these are anticipatory bumps for future versions, they should wait until the versions are actually released.

The bumps that look correct:

  • codecov/codecov-action@v5
  • benchmark-action/github-action-benchmark@v1.20.7 (pinned to specific version — good practice)
  • docker/build-push-action@v6
  • peter-evans/dockerhub-description@v5
  • google-github-actions/auth@v3 and setup-gcloud@v3
  • actions-rust-lang/setup-rust-toolchain@v1.15.2 (pinned — good)

Could you confirm the @v6/@v7 tags exist on the actions/* repos?

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