Updated actions SHAs to latest release

[Naveen-Pal]

Resolves #1210

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Streamlined internal build and deployment processes by updating automation tools, enhancing reliability and performance for the overall release cycle.

Walkthrough

This pull request updates the CI/CD workflow file by replacing outdated commit hashes with the latest release versions for multiple GitHub Actions. The updates include versions for pnpm/action-setup, actions/setup-node, docker/setup-buildx-action, and docker/setup-qemu-action within the workflow configuration.

Changes

File(s)	Change Summary
.github/workflows/run-ci-cd.yaml	Updated commit hashes for pnpm/action-setup, actions/setup-node, docker/setup-buildx-action, and docker/setup-qemu-action to their latest released versions.

Assessment against linked issues

Objective	Addressed	Explanation
Update actions commit hash with latest releases (#1210)	✅

Possibly related PRs

• Pin Github actions to specific commit #1195: Related update of GitHub Actions versions in the CI/CD workflow, specifically addressing pnpm/action-setup and actions/setup-node.

Suggested labels

ci

Suggested reviewers

• arkid15r

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f2389a8 and 356a511.

📒 Files selected for processing (1)

• .github/workflows/run-ci-cd.yaml (6 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Run frontend e2e tests

🔇 Additional comments (8)

.github/workflows/run-ci-cd.yaml (8)

55-56: Action Update: pnpm/action-setup SHA Updated

The SHA for the pnpm Action is updated to a7487c7e89a18df4991f7f222e4898a00d66ddda, ensuring the workflow now uses the latest published version. Please review the upstream release notes for any behavior changes or new configuration options.

---

61-65: Action Update: actions/setup-node SHA Updated

The Node.js setup action is now referenced with SHA cdca7365b2dadb8aad0a33bc7601856ffabcc48e. Confirm that the specified node version (22) and caching parameters remain fully compatible with this updated version.

---

105-106: Action Update: docker/setup-buildx-action SHA (Backend Tests) Updated

The buildx action used in the "run-backend-tests" job is updated to b5ca514318bd6ebac0aedd5d36ec1b5c232a2. Ensure that previously configured caching strategies and build configurations behave as expected with the new version.

---

131-132: Action Update: docker/setup-buildx-action SHA (Frontend Unit Tests) Updated

The docker/setup-buildx-action in the "run-frontend-unit-tests" job now uses the SHA b5ca514318bd6ebac0aedd5d36ec1b5c232a2. It’s advisable to double-check that the build caching and multi-platform builds continue to work correctly after this update.

---

157-158: Action Update: docker/setup-buildx-action SHA (Frontend E2E Tests) Updated

The updated SHA (b5ca514318bd6ebac0aedd5d36ec1b5c232a2) for the buildx action in the E2E tests job should offer improved stability. Validate that there are no regressions in Docker build performance or configuration nuances.

---

189-190: Action Update: docker/setup-qemu-action SHA (Staging) Updated

The QEMU setup action is now pointed to SHA 29109295f81e9208d7d86ff1c6c12d2833863392. This version update is expected to enhance emulation support; make sure it integrates smoothly with your buildx configurations.

---

350-351: Action Update: docker/setup-qemu-action SHA (Production) Updated

In the production build job, the QEMU action now uses the updated SHA 29109295f81e9208d7d86ff1c6c12d2833863392. Verify that the change does not introduce platform compatibility issues and that emulation performance meets production needs.

---

353-354: Action Update: docker/setup-buildx-action SHA (Production) Updated

The buildx action in the production images build step is updated to SHA b5ca514318bd6ebac0aedd5d36ec1b5c232a2. Please confirm that build caching, multi-platform builds, and overall Docker build procedures are functioning as expected post-update.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Naveen-Pal]

For reference:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[arkid15r]

LGTM