Update Github Actions workflow to v4

[justanwar]

PR intention

Github is deprecating actions/checkout, download-artifact, and upload-artifact v1 and v2.

Code changes brief

Updates actions/checkout, download-artifact, and upload-artifact to v4. This will also reduce the warnings in Actions.

Closes #1459.

[coderabbitai]

Walkthrough

The changes update the GitHub Actions workflow configuration to use newer versions of the checkout and upload-artifact actions and replace an environment variable for better clarity. These modifications ensure continued functionality and improved consistency as older action versions are deprecated.

Changes

Files	Change Summary
.github/workflows/ci-master.yml	Updated ARTIFACT_DIR to SOURCE_ARTIFACT_DIR, changed actions/checkout and actions/upload-artifact to v4.

Assessment against linked issues

Objective	Addressed	Explanation
Update actions/upload-artifact to avoid deprecation (#1459)	✅
Update actions/checkout to a newer version (#1459)	✅

Poem

In the world of Actions, we now renew,
With checkout and artifact brought up to view.
Gone are the old, deprecated ways,
Source artifacts now shine in these days.
With paths refined and clarity in sight,
Our workflows soar, efficient and bright.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between bcaacd4 and 173beb7.

Files selected for processing (1)

• .github/workflows/ci-master.yml (9 hunks)

Additional comments not posted (11)

.github/workflows/ci-master.yml (11)

17-17: Updated environment variable for clarity.

The change from ARTIFACT_DIR to SOURCE_ARTIFACT_DIR enhances clarity and aligns with the naming convention that explicitly states the purpose of the directory.

---

24-24: Updated checkout action to v4.

This update is necessary to keep the workflow compatible with the latest GitHub Actions features and to avoid deprecation issues.

---

40-41: Proper use of the updated environment variable in directory operations.

The script correctly uses the SOURCE_ARTIFACT_DIR for directory operations, ensuring that the environment variable update is consistently applied throughout the workflow.

---

43-46: Updated upload-artifact action to v4 with correct environment variable usage.

The action version update and the use of SOURCE_ARTIFACT_DIR ensure that the workflow remains up-to-date and functionally correct.

---

56-59: Updated download-artifact action to v4.

The update to v4 for the download-artifact action aligns with the necessary changes to maintain functionality post-deprecation of older versions.

---

90-90: Consistent update of upload-artifact action across different jobs.

The use of actions/upload-artifact@v4 in the Linux build job ensures consistency and up-to-date functionality across the workflow.

---

111-111: Updated upload-artifact action for test logs.

Updating this action to v4 for handling test logs ensures that all artifact-related actions are consistent and modernized.

---

123-126: Ensured consistency in artifact handling for Windows builds.

The update to actions/download-artifact@v4 and the use of SOURCE_ARTIFACT_DIR maintain consistency and ensure the workflow is using the latest supported actions.

---

153-153: Updated upload-artifact action for Windows binaries.

This update ensures that the Windows build artifacts are handled using the latest version of the upload-artifact action, maintaining consistency and avoiding deprecation issues.

---

165-168: Updated download-artifact action for macOS builds.

The consistent update across different platform builds ensures that all artifact downloads use the latest action version, aligning with the overall update strategy of the workflow.

---

194-194: Updated upload-artifact action for macOS binaries.

This final update of the upload-artifact action for macOS binaries confirms the thorough application of the necessary updates across all relevant parts of the workflow.